From: Sasha Levin <sashal@kernel.org>
To: Shung-Hsi Yu <shung-hsi.yu@suse.com>
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: Patches not posted as reply to stable-rc reviews (was "Re: [PATCH 6.18 000/757] 6.18.16-rc2 review")
Date: Tue, 10 Mar 2026 05:48:33 -0400 [thread overview]
Message-ID: <aa_o8WKGFjhRUPgx@laps> (raw)
In-Reply-To: <iy7dogrbld3h5ygezzkhp3sebokfibu5suegpidlsrmp2ibfwd@fvstv7j7dcfm>
On Tue, Mar 10, 2026 at 11:16:37AM +0800, Shung-Hsi Yu wrote:
>Hi Sasha,
>
>On Mon, Mar 02, 2026 at 11:08:53AM -0500, Sasha Levin wrote:
>> This is the start of the stable review cycle for the 6.18.16 release.
>> There are 757 patches in this series, all will be posted as a response
>> to this one...
>
>It seems that patches were not posted as response. It was for 6.19, but
>not for the rest (6.18, 6.12, 6.6, 6.1, 5.15, and 5.10).
Yup, they ended up going only to patches@. I've fixed that.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-03-10 9:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 16:08 [PATCH 6.18 000/757] 6.18.16-rc2 review Sasha Levin
2026-03-02 19:35 ` Brett A C Sheffield
2026-03-02 21:51 ` Brett Mastbergen
2026-03-02 22:14 ` Justin Forbes
2026-03-02 23:55 ` Peter Schneider
2026-03-03 5:24 ` Florian Fainelli
2026-03-03 8:21 ` Shung-Hsi Yu
2026-03-03 8:31 ` Barry K. Nathan
2026-03-03 12:03 ` Ron Economos
2026-03-03 14:12 ` Jon Hunter
2026-03-03 18:27 ` Mark Brown
2026-03-03 19:05 ` Shuah Khan
2026-03-03 21:38 ` Miguel Ojeda
2026-03-04 6:19 ` Hardik Garg
2026-03-10 3:16 ` Patches not posted as reply to stable-rc reviews (was "Re: [PATCH 6.18 000/757] 6.18.16-rc2 review") Shung-Hsi Yu
2026-03-10 9:48 ` Sasha Levin [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=aa_o8WKGFjhRUPgx@laps \
--to=sashal@kernel.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--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=shung-hsi.yu@suse.com \
--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