Hi,
Bernie Thompson wrote:
> On Sun, May 20, 2012 at 5:41 PM, Ben Hutchings <[email protected]> wrote:
>> Any reason why this shouldn't go into 3.2.y as well? The driver doesn't
>> appear to have changed in any significant way between 3.2 and 3.3.
>
> Hi Ben - Thanks for asking. There are just two commits missing
> between 3.2 and 3.3
>
> I thought it might conflict with Greg's commit:
A more basic question is whether there are semantic reasons not to
include it in particular releases. (Checking for textual conflicts
is pretty easy. :))
The new patch description says:
Prior to this patch, were doing too much in
USB
probe(), including starting big transfers to paint the screen of the USB
graphics device.
However that doesn't explain changes like moving the acquisition of
dev->kfref about 30 lines down. Can you explain what the part of the
patch preventing a panic does, for example by providing an example
trace of the panic? This would make it easier to see how to safely
backport the fix and which kernels need it.
Thanks and hope that helps,
Jonathan
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
