On Mon, Nov 26, 2012 at 02:11:20PM +0100, Florian Fainelli wrote:
> On Saturday 24 November 2012 19:19:34 Jonas Gorski wrote:

> > Well, I noticed this particular problem on a 3.6 kernel (3.6.7 to be
> > exact), so by that definition at least one noticed, unless I don't
> > count as anyone ;-). So, how can I make this driver less broken for
> > release kernels? I somewhat doubt the framework change will be picked
> > up by release kernel maintainers.

> Considering it is a simple one-liner in spi-bcm63xx and that you don't want to
> propagate a framework-level change back to -stable (which makes sense), don't
> you want to pick that one?

> At least two other users told me about this bug in private conversations.

Feel free to submit it for stable but it doesn't seem sensible to apply
it to development kernels, we want to remove this code from individual
drivers not add new copies.

Attachment: signature.asc
Description: Digital signature

Reply via email to