From: Sasha Levin <sashal@kernel.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
gregkh@linuxfoundation.org, patches@lists.linux.dev,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@nabladev.com,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 5.10 000/334] 5.10.252-rc2 review
Date: Sun, 8 Mar 2026 13:55:34 -0400 [thread overview]
Message-ID: <aa24FjFgdgLQueBx@laps> (raw)
In-Reply-To: <552119600ffc7b417c55c18d7fd8c236e0bb1626.camel@decadent.org.uk>
On Sun, Mar 08, 2026 at 11:26:00AM +0100, Ben Hutchings wrote:
>On Sat, 2026-03-07 at 08:20 -0500, Sasha Levin wrote:
>> On Fri, Mar 06, 2026 at 08:19:01PM +0100, Ben Hutchings wrote:
>> > On Mon, 2026-03-02 at 11:10 -0500, Sasha Levin wrote:
>> > > This is the start of the stable review cycle for the 5.10.252 release.
>> > > There are 334 patches in this series, all will be posted as a response
>> > > to this one.
>> >
>> > And yet they were not.
>>
>> I don't think we ever did post the series for -rc2+, did we?
>[...]
>
>The patches for rc1 also weren't sent, or at least none of them reached
>the stable list. And rc2 normally only adds or removes a small number
Ah, I see what happened. I'll add stable@. They were only sent to patches@:
https://lore.kernel.org/all/20260228181736.1605592-1-sashal@kernel.org/
>of patches identified in the review of rc1, but this rc2 added nearly
>200 for no clear reason.
There's an explanation here: https://lore.kernel.org/all/aaWqrI1fLkusYqMV@laps/
But yes, maybe I should have re-sent the entire patch series given the change.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-03-08 17:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 16:10 [PATCH 5.10 000/334] 5.10.252-rc2 review Sasha Levin
2026-03-02 18:35 ` Florian Fainelli
2026-03-02 19:35 ` Brett A C Sheffield
2026-03-02 20:16 ` Woody Suwalski
2026-03-03 14:12 ` Jon Hunter
2026-03-03 19:42 ` Mark Brown
2026-03-04 1:33 ` Barry K. Nathan
2026-03-06 19:19 ` Ben Hutchings
2026-03-07 13:20 ` Sasha Levin
2026-03-08 10:26 ` Ben Hutchings
2026-03-08 17:55 ` Sasha Levin [this message]
2026-03-26 13:13 ` Ben Hutchings
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=aa24FjFgdgLQueBx@laps \
--to=sashal@kernel.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--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@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--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