All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Greg KH <greg@kroah.com>
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: Request to apply commit c4005a8f65ed to the -stable kernels
Date: Tue, 19 Jan 2021 10:51:45 -0500	[thread overview]
Message-ID: <20210119155145.GB173923@rowland.harvard.edu> (raw)
In-Reply-To: <83ed9f3929bd064b54bb9903cd489adde442e1c7.camel@alliedtelesis.co.nz>

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?

Thanks,

Alan Stern

  reply	other threads:[~2021-01-19 15:53 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       ` Alan Stern [this message]
2021-01-19 18:11         ` Request to apply commit c4005a8f65ed to the -stable kernels Greg KH
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=20210119155145.GB173923@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --cc=Hamish.Martin@alliedtelesis.co.nz \
    --cc=greg@kroah.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=paul.kocialkowski@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.