[PATCH] mac80211: fix deferred hardware scan requests
Luis R. Rodriguez
mcgrof at gmail.com
Tue Apr 20 19:28:01 UTC 2010
On Fri, Apr 16, 2010 at 4:42 PM, Stefan Bader
<stefan.bader at canonical.com> wrote:
> Chase Douglas wrote:
>> On Fri, Apr 16, 2010 at 4:29 PM, Stefan Bader
>> <stefan.bader at canonical.com> wrote:
>>> Despite of likely knowing the intention I need to play dumb: what is the
>>> intention of this? There is not much indication which release you target,
>>> neither much help about the impact of the bug or the regression potential of the
>>> fix. What is the use case to trigger it.
>>> As we basically are locked down with the release kernel, we are now doing all
>>> fixes in SRU mode which requires a bit more explanation on things (see Leann's
>>> recent submissions).
>>> If this only triggers a warning but still leaves things workable, this should
>>> hopefully get back via stable. As normal SRU updates are in general limited to
>>> more serious issues.
>> Ok. I saw Leann with the SRU and forgot we are in that mode now. So do
>> we prefer the SRU justification in the patch email like Leann
>> provided, or in the bug report. The wiki page indicates that it should
>> be done in the bug report, but maybe we do things different in the
> In the bug report primarily (best by modifying the description so it is right at
> the top). But I found it good to be in the mail as well (usually right copied
> from the bug report) as it saves one from needing to go to launchpad to
> understand the reasoning.
>> I think the issue doesn't take down the system, so once apport is
>> disabled for the release this probably won't be a big deal. I think we
>> should probably just wait for it to come from -stable assuming it
>> isn't rejected.
>> -- Chase
> Ok thanks. Stefan
If there are good reasons to push this into a distribution for stable
kernel inclusion might as well send the same request to
stable at kernel.org and cc linux-wireless for the request. You should
provide the details for your justification. This would then trickle
down to Ubuntu from the stable kernel series.
If this issues is causing to fill up your logs that is good enough
justification for a stable fix propagation.
More information about the kernel-team