From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, Benjamin Berg <benjamin@sipsolutions.net>
Cc: patches@lists.linux.dev, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@denx.de,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.13 000/197] 6.13.7-rc2 review
Date: Tue, 11 Mar 2025 18:45:35 +0100 [thread overview]
Message-ID: <00f382c4-1347-bc6d-b3ec-427de5658cf5@applied-asynchrony.com> (raw)
In-Reply-To: <20250311144241.070217339@linuxfoundation.org>
On 2025-03-11 15:48, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.13.7 release.
> There are 197 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
Still missing a followup for iwlwifi as mentioned on rc1:
https://lore.kernel.org/stable/5d129bda966b7a55b444f4d48f225038361e9253.camel@sipsolutions.net/
Not sure if that refers to the whole series or only the first patch,
maybe Benjamin can clarify.
cheers
Holger
next prev parent reply other threads:[~2025-03-11 17:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 14:48 Greg Kroah-Hartman
2025-03-11 15:15 ` Ronald Warsow
2025-03-11 17:45 ` Holger Hoffstätte [this message]
2025-03-11 20:17 ` Benjamin Berg
2025-03-12 7:46 ` Greg Kroah-Hartman
2025-03-11 18:12 ` Jon Hunter
2025-03-12 9:35 ` Luna Jernberg
2025-03-11 19:20 ` Florian Fainelli
2025-03-11 19:23 ` Miguel Ojeda
2025-03-12 0:25 ` Peter Schneider
2025-03-12 10:25 ` Naresh Kamboju
2025-03-12 10:52 ` Takeshi Ogasawara
2025-03-12 12:31 ` Mark Brown
2025-03-12 12:41 ` Justin Forbes
2025-03-12 17:28 ` Hardik Garg
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=00f382c4-1347-bc6d-b3ec-427de5658cf5@applied-asynchrony.com \
--to=holger@applied-asynchrony.com \
--cc=akpm@linux-foundation.org \
--cc=benjamin@sipsolutions.net \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®