Dear Greg,
Thanks for the promptly reply.
> -----Original Message-----
> From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, December 19, 2019 4:29 PM
> To: Lee, Chiasheng <chiasheng.lee@xxxxxxxxx>
> Cc: stable@xxxxxxxxxxxxxxx; Mathias Nyman <mathias.nyman@xxxxxxxxxxxxxxx>;
> Guenter Roeck <groeck@xxxxxxxxxxxx>; Lee, Hou-hsun <hou-
> hsun.lee@xxxxxxxxx>; Pan, Harry <harry.pan@xxxxxxxxx>
> Subject: Re: Please apply commit 057d476fff778f1 ("xhci: fix USB3 device
> initiated resume race with roothub autosuspend") to v4.4.y and v4.14.y
>
> On Thu, Dec 19, 2019 at 08:20:12AM +0000, Lee, Chiasheng wrote:
> > Hi,
> >
> > Commit 057d476fff778f1 ("xhci: fix USB3 device initiated resume race
> > with roothub autosuspend") fixes race conditions when we're dealing with a
> USB3 modem using v4.4 and USB3 hubs using 4.14.
> > Kindly apply the patch to v4.4.y and v4.14.y.
>
> Why not 4.9.y and 4.19.y? You can not just skip stable kernel trees, otherwise
> people upgrading will have a regression.
I (mistakenly?) thought it would be merged automagically to all the stable branches since stable@xxxxxxxxxxxxxxx is in the CC list.
And we encountered, root-caused, and fixed/verified the issue only with v4.4 and v4.14 Chromium OS kernel.
>
> Anyway, the reason I did not backport the patch to older kernels is that it does
> not apply at all. If you have already done the backport (and I am guessing you
> have as otherwise how would you have tested this), please provide it to us so
> that we can apply it to all trees.
We did the backport to Chromium OS kernel v4.4 and v4.14 for test indeed. Will check with our colleagues and get back to you soon.
>
> thanks,
>
> greg k-h
Thanks,
Chiasheng
