From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
akpm@linux-foundation.org, torvalds@linux-foundation.org
Cc: lwn@lwn.net, jslaby@suse.cz, gregkh@linuxfoundation.org
Subject: Linux 6.1.166
Date: Thu, 5 Mar 2026 10:13:02 -0500 [thread overview]
Message-ID: <20260305151303.676629-1-sashal@kernel.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I'm announcing the release of the 6.1.166 kernel.
Only upgrade if you've observed a build failure with 6.1.165.
The updated 6.1.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-6.1.y
and can be browsed at the normal kernel.org git web browser:
https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
Thanks,
Sasha
- ------------
Makefile | 2 +-
arch/x86/kernel/setup.c | 6 ------
2 files changed, 1 insertion(+), 7 deletions(-)
Sasha Levin (2):
Revert "x86/kexec: add a sanity check on previous kernel's ima kexec buffer"
Linux 6.1.166
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE4n5dijQDou9mhzu83qZv95d3LNwFAmmpnXQACgkQ3qZv95d3
LNwr7w/9F5TY7FuvSVSYHJP0SHmbgS2BtSBoZRdEDOJWehnjVxYaS94j9wMPT+2e
Cs8tASGXMllSPEajiI7AgMXjuI3vxRwDN2vk0TvCw1Yt6dQVfPBuwftzy8KX1AC3
ljMv1yQCyyca1+PDTlRlOyU0VP1m41RlIzjq/Gg+S3rAJWMA3vlhwjAUZqB2cpmX
sFmY5QzFCVar/wdfM/csJ/1MEkig2gMJgFGWS3TyB7+ElfkSBlmtdtKZiSbI4Slr
YpTlN+t0NtcuvDwBpPaF71Fds9vpCPnEOQ+K5jHz4a6jlcbqs+8onxdjW7A8DgfT
UYPFKul19kOWJ76A1YVFNhsvhD4VAnssnq4t2TXj1n2YVBz8+0wGnPsEMouNUHWA
aA6719tnfn2+Fqkx+SFrYCYBTCexLY/EOjINmyY5vuwJO629yFev7j3atEHJpYQl
ALQX4VbaemSHyYmqR51dVNNO0y624gqw1uMW1FD4t46/BGsH9B85/yNrkjBysTJQ
8pa+5jRYWRUXF779qvUp1jVqmLH4qyMXmK3uH7aOTaVJqxHPjGWIkugLQr0Xr8aA
TVytfLpFw1zL+ujbI4HujOQUTV3KrVt5dspZ+pKYV6UD1iMEekudm/trDXAE5N2r
iJ9mnxlKwsAWBGLzjLPIKL/8w6n7ckmINPlJksdAJsEV9vmzfB0=
=diwW
-----END PGP SIGNATURE-----
next reply other threads:[~2026-03-05 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 15:13 Sasha Levin [this message]
2026-03-05 15:13 ` Linux 6.1.166 Sasha Levin
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=20260305151303.676629-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--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