From: Sasha Levin <sashal@kernel.org>
To: Peter Schneider <pschneider1968@googlemail.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
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 6.1 000/533] 6.1.165-rc2 review
Date: Mon, 2 Mar 2026 13:09:25 -0500 [thread overview]
Message-ID: <aaXSVaGrwY-k80m5@laps> (raw)
In-Reply-To: <abe2fb5f-61b3-4597-b27b-c6c61f5efc7d@googlemail.com>
On Mon, Mar 02, 2026 at 06:57:53PM +0100, Peter Schneider wrote:
>Am 02.03.2026 um 18:48 schrieb Sasha Levin:
>[...]
>
>>I'll drop it and push the -rc2 branch again for all affected kernels.
>>
>
>Wouldn't it better to push a -rc3 branch then, so as to not create confusion? (I'm confused now... 🤔🙄)
>
>Or did you actually mean rc3?
>
>Also, the causing patch ("x86/kexec: add a sanity check on previous
>kernel's ima kexec buffer") is in all others 6.x.y -rc2s from today,
>so maybe Harshit should quickly check to which 6.x.y stable branches
>this patch was meant to be backported/included?
I just force pushed a new -rc2, and dropped the offending patch from all
branches for now.
This one will end up being a slightly bigger release, and we can revisit this
commit and any others we had to drop for the next cycle.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-03-02 18:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 16:09 [PATCH 6.1 000/533] 6.1.165-rc2 review Sasha Levin
2026-03-02 17:26 ` Peter Schneider
2026-03-02 17:36 ` Harshit Mogalapalli
2026-03-02 17:49 ` Sasha Levin
2026-03-02 17:58 ` Harshit Mogalapalli
2026-03-02 18:07 ` Sasha Levin
2026-03-02 17:48 ` Sasha Levin
2026-03-02 17:57 ` Peter Schneider
2026-03-02 18:09 ` Sasha Levin [this message]
2026-03-02 18:15 ` Peter Schneider
2026-03-02 19:46 ` Brett A C Sheffield
2026-03-02 20:12 ` Peter Schneider
2026-03-02 19:35 ` Brett A C Sheffield
2026-03-02 19:55 ` Peter Schneider
2026-03-03 4:52 ` Florian Fainelli
2026-03-03 7:34 ` Francesco Dolcini
2026-03-03 12:26 ` Ron Economos
2026-03-03 14:12 ` Jon Hunter
2026-03-03 19:37 ` Mark Brown
2026-03-03 21:18 ` Miguel Ojeda
2026-03-04 6:14 ` Hardik Garg
2026-03-04 17:47 ` Shuah Khan
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=aaXSVaGrwY-k80m5@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=harshit.m.mogalapalli@oracle.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=pschneider1968@googlemail.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