From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
Sasha Levin <sashal@kernel.org>,
Minas Harutyunyan <hminas@synopsys.com>
Subject: Re: Patch "usb: dwc2: Skip clock gating on Broadcom SoCs" has been added to the 6.11-stable tree
Date: Tue, 1 Oct 2024 10:24:28 +0200 [thread overview]
Message-ID: <2024100118-setup-douche-b883@gregkh> (raw)
In-Reply-To: <17c9e4c6-260a-40c9-be1f-4f67ec6d5e3b@gmx.net>
On Tue, Oct 01, 2024 at 07:23:16AM +0200, Stefan Wahren wrote:
> Hi Sasha,
>
> Am 01.10.24 um 01:26 schrieb Sasha Levin:
> > This is a note to let you know that I've just added the patch titled
> >
> > usb: dwc2: Skip clock gating on Broadcom SoCs
> >
> > to the 6.11-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-dwc2-skip-clock-gating-on-broadcom-socs.patch
> > and it can be found in the queue-6.11 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.
> please do not apply this patch to any stable branch yet. Recently i
> discovered a critical issue [1] which is revealed by this change. This
> needs to be investigated and fixed before this patch can be applied.
Now dropped from all stable trees, thanks.
greg k-h
prev parent reply other threads:[~2024-10-01 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240930232610.2570738-1-sashal@kernel.org>
2024-10-01 5:23 ` Patch "usb: dwc2: Skip clock gating on Broadcom SoCs" has been added to the 6.11-stable tree Stefan Wahren
2024-10-01 8:24 ` Greg Kroah-Hartman [this message]
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=2024100118-setup-douche-b883@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hminas@synopsys.com \
--cc=sashal@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=wahrenst@gmx.net \
/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