From: Greg KH <greg@kroah.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Hamish Martin <Hamish.Martin@alliedtelesis.co.nz>,
"paul.kocialkowski@bootlin.com" <paul.kocialkowski@bootlin.com>,
stable@vger.kernel.org,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: Request to apply commit c4005a8f65ed to the -stable kernels
Date: Tue, 19 Jan 2021 19:11:38 +0100 [thread overview]
Message-ID: <YAcg2pklrTlaTinX@kroah.com> (raw)
In-Reply-To: <20210119155145.GB173923@rowland.harvard.edu>
On Tue, Jan 19, 2021 at 10:51:45AM -0500, Alan Stern wrote:
> Greg:
>
> Hamish Martin has reported a problem caused by applying commit
> b77d2a0a223b ("usb: ohci: Default to per-port over-current protection")
> to the -stable kernel series without also applying commit c4005a8f65ed
> ("usb: ohci: Make distrust_firmware param default to false").
>
> Can we please queue up commit c4005a8f65ed for all the -stable kernel
> branches which already merged versions of commit b77d2a0a223b?
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2021-01-19 18:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 21:25 [PATCH v2 1/2] usb: ohci: Default to per-port over-current protection Hamish Martin
2020-09-10 21:25 ` [PATCH v2 2/2] usb: ohci: Make distrust_firmware param default to false Hamish Martin
2020-09-11 15:17 ` Alan Stern
2020-09-11 15:17 ` [PATCH v2 1/2] usb: ohci: Default to per-port over-current protection Alan Stern
2020-12-27 11:22 ` Paul Kocialkowski
2021-01-09 21:26 ` Alan Stern
2021-01-19 1:09 ` Hamish Martin
2021-01-19 15:51 ` Request to apply commit c4005a8f65ed to the -stable kernels Alan Stern
2021-01-19 18:11 ` Greg KH [this message]
2021-01-20 10:50 ` [PATCH v2 1/2] usb: ohci: Default to per-port over-current protection paul.kocialkowski
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=YAcg2pklrTlaTinX@kroah.com \
--to=greg@kroah.com \
--cc=Hamish.Martin@alliedtelesis.co.nz \
--cc=linux-usb@vger.kernel.org \
--cc=paul.kocialkowski@bootlin.com \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).