From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Lee, Chiasheng" <chiasheng.lee@intel.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Guenter Roeck <groeck@chromium.org>,
"Lee, Hou-hsun" <hou-hsun.lee@intel.com>,
"Pan, Harry" <harry.pan@intel.com>
Subject: Re: Please apply commit 057d476fff778f1 ("xhci: fix USB3 device initiated resume race with roothub autosuspend") to v4.4.y and v4.14.y
Date: Thu, 19 Dec 2019 11:10:40 +0200 [thread overview]
Message-ID: <2b70a289-d35f-eecb-c230-e6b85f42c990@linux.intel.com> (raw)
In-Reply-To: <20191219082900.GA1015381@kroah.com>
On 19.12.2019 10.29, Greg Kroah-Hartman wrote:
> 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.
>
> 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.
>
Let me fix up and submit the backport, give me a few minutes.
I'll check it applies to the other stable trees as well.
-Mathias
next prev parent reply other threads:[~2019-12-19 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 8:20 Please apply commit 057d476fff778f1 ("xhci: fix USB3 device initiated resume race with roothub autosuspend") to v4.4.y and v4.14.y Lee, Chiasheng
2019-12-19 8:29 ` Greg Kroah-Hartman
2019-12-19 9:10 ` Mathias Nyman [this message]
2019-12-19 9:12 ` Lee, Chiasheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2b70a289-d35f-eecb-c230-e6b85f42c990@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=chiasheng.lee@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=harry.pan@intel.com \
--cc=hou-hsun.lee@intel.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox