From: Daniel Wagner <wagi@monom.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
stable-rt@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Clark Williams <williams@redhat.com>,
Daniel Wagner <wagi@monom.org>
Subject: [PATCH RT 0/1] Linux v4.19.306-rt132-rc1
Date: Fri, 2 Feb 2024 18:04:56 +0100 [thread overview]
Message-ID: <20240202170457.29516-1-wagi@monom.org> (raw)
Dear RT Folks,
This is the RT stable review cycle of patch 4.19.306-rt132-rc1.
I reverted one -rt specific commit to be able to merge the 4.19.306
release:
0cb152421350 ("crypto: scompress - serialize RT percpu scratch buffer access with a local lock")
because the stable backport
f8f261f9ade2 ("crypto: scompress - Use per-CPU struct instead multiple variables")
seems to make the downstream -rt fix unnecessary.
Please scream at me if I messed something up. Please test the patches
too.
The -rc release is also available on kernel.org
https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
on the v4.19-rt-next branch.
If all goes well, this patch will be converted to the next main
release on 2024-02-09.
Signing key fingerprint:
5BF6 7BC5 0826 72CA BB45 ACAE 587C 5ECA 5D0A 306C
All keys used for the above files and repositories can be found on the
following git repository:
git://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git
Enjoy!
Daniel
next reply other threads:[~2024-02-02 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 17:04 Daniel Wagner [this message]
2024-02-02 17:04 ` [PATCH] Revert "crypto: scompress - serialize RT percpu scratch buffer access with a local lock" Daniel Wagner
2024-02-05 8:21 ` [PATCH RT 0/1] Linux v4.19.306-rt132-rc1 Sebastian Andrzej Siewior
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=20240202170457.29516-1-wagi@monom.org \
--to=wagi@monom.org \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable-rt@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
--cc=williams@redhat.com \
/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