From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Johan Hovold <johan@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
stable-commits@vger.kernel.org, johan+linaro@kernel.org,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Felipe Balbi <balbi@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Patch "usb: dwc3: qcom: fix peripheral and OTG suspend" has been added to the 5.19-stable tree
Date: Sat, 24 Sep 2022 11:14:57 +0200 [thread overview]
Message-ID: <Yy7KkehWhnQL9UBo@kroah.com> (raw)
In-Reply-To: <Yy7GS22UBJt4SK1H@hovoldconsulting.com>
On Sat, Sep 24, 2022 at 10:56:43AM +0200, Johan Hovold wrote:
> FFS, Sasha...
>
> On Fri, Sep 23, 2022 at 12:55:34PM -0400, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > usb: dwc3: qcom: fix peripheral and OTG suspend
> >
> > to the 5.19-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > usb-dwc3-qcom-fix-peripheral-and-otg-suspend.patch
> > and it can be found in the queue-5.19 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> Stop pulling in these dwc3 patches! I already spent an afternoon doing
> backports for all the stable trees so that you wouldn't pull in half the
> world as dependencies.
>
> This fixes an issue with a commit in 6.0, which should not be backported
> in the first place.
>
> Just as I told you two weeks ago when these were dropped the last time:
>
> https://lore.kernel.org/lkml/YxbfJqPb8x0WjmqR@hovoldconsulting.com/
>
> If you can't fix up the trivial context change yourself, then use one of
> the backports of:
>
> https://lore.kernel.org/lkml/20220906120702.19219-3-johan@kernel.org/
>
> or simply just leave it out as the issue can't be triggered in 5.19
> currently.
>
> Just drop all the dwc3 patches from the pending-5.19 branch.
Now dropped, except for the one I added yesterday :)
thanks,
greg k-h
next prev parent reply other threads:[~2022-09-24 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220923165534.652593-1-sashal@kernel.org>
2022-09-24 8:56 ` Patch "usb: dwc3: qcom: fix peripheral and OTG suspend" has been added to the 5.19-stable tree Johan Hovold
2022-09-24 9:14 ` Greg Kroah-Hartman [this message]
2022-09-24 9:22 ` Johan Hovold
[not found] <20220905125309.1037700-1-sashal@kernel.org>
[not found] ` <YxXyd5H9TLWKUbWy@hovoldconsulting.com>
[not found] ` <YxXz7LBh5Y4DSd4W@sashalap>
[not found] ` <YxX15QkMDV+0amk8@hovoldconsulting.com>
[not found] ` <YxX29eiH0qyyRk9x@sashalap>
[not found] ` <YxX4QT6eeRiatmX+@hovoldconsulting.com>
[not found] ` <YxX7R/EAynZC/iGr@sashalap>
2022-09-05 15:07 ` Greg Kroah-Hartman
[not found] ` <YxYO+u0rAg029yNl@hovoldconsulting.com>
[not found] ` <YxYrS3z/nYFYzoTh@sashalap>
2022-09-05 17:57 ` Greg Kroah-Hartman
2022-09-06 5:48 ` Johan Hovold
2022-09-06 6:46 ` Greg Kroah-Hartman
2022-09-06 7:01 ` Johan Hovold
2022-09-06 11:22 ` Greg Kroah-Hartman
2022-09-06 12:09 ` Johan Hovold
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=Yy7KkehWhnQL9UBo@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=agross@kernel.org \
--cc=balbi@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=johan@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable-commits@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.