On Mon, 2012-05-21 at 00:38 -0500, Jonathan Nieder wrote:
> Hi,
>
> Bernie Thompson wrote:
> > On Sun, May 20, 2012 at 5:41 PM, Ben Hutchings 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
On Sun, May 20, 2012 at 05:23:38PM -0700, ber...@plugable.com wrote:
> From: Bernie Thompson
>
> This is a request to backport a 3.4 udlfb driver patch to 3.3.*
>
> Existing upstream (3.4) commit ID: 8d21547d3c9c3bc653261f26d554cfabc4a083de
>
> This patch fixes a critical panic (in hcd_buffer_
Hi Jonathan,
On Sun, May 20, 2012 at 10:38 PM, Jonathan Nieder wrote:
> However that doesn't explain changes like moving the acquisition of
> dev->kfref about 30 lines down.
There's an extra dereference on the error path that should get a patch
in 3.5/3.6.
> Can you explain what the part of the
Hi,
Bernie Thompson wrote:
> On Sun, May 20, 2012 at 5:41 PM, Ben Hutchings 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
On Sun, May 20, 2012 at 5:41 PM, Ben Hutchings 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 m
On Sun, 2012-05-20 at 17:23 -0700, ber...@plugable.com wrote:
> From: Bernie Thompson
>
> This is a request to backport a 3.4 udlfb driver patch to 3.3.*
[...]
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