From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
stable-rt <stable-rt@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Daniel Wagner <daniel.wagner@suse.com>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Clark Williams <williams@redhat.com>,
Mark Gross <markgross@kernel.org>, Pavel Machek <pavel@denx.de>,
Jeff Brady <jeffreyjbrady@gmail.com>
Subject: Re: [ANNOUNCE] 5.10.234-rt126
Date: Fri, 21 Feb 2025 10:50:04 +0100 [thread overview]
Message-ID: <26f102f6-4e35-4267-b6ec-9ebd0c7572f7@siemens.com> (raw)
In-Reply-To: <Z7ZWPGBt4Pv9o54T@uudg.org>
On 19.02.25 23:07, Luis Claudio R. Goncalves wrote:
> Hello RT-list!
>
> I'm pleased to announce the 5.10.234-rt126 stable release.
>
> This release is just an update to the new stable 5.10.234 version and
> no RT-specific changes have been made.
>
Was [1] coming too late for this release cycle?
We may have run into this bug independently a second time here, I just
don't know the exact kernel version yet. However, we do know that 5.10
needs the fix as well.
Jan
> You can get this release via the git tree at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
>
> branch: v5.10-rt
> Head SHA1: 5c5f37fc0ab0914da38776700e77a46ca3e30bf6
>
> Or to build 5.10.234-rt126 directly, the following patches should be applied:
>
> https://www.kernel.org/pub/linux/kernel/v5.x/linux-5.10.tar.xz
>
> https://www.kernel.org/pub/linux/kernel/v5.x/patch-5.10.234.xz
>
> https://www.kernel.org/pub/linux/kernel/projects/rt/5.10/older/patch-5.10.234-rt126.patch.xz
>
> Signing key fingerprint:
>
> 9354 0649 9972 8D31 D464 D140 F394 A423 F8E6 7C26
>
> 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!
> Luis
>
[1]
https://lore.kernel.org/stable-rt/CAMLffL-PTp+Y-rXsTFaC5cUJyMMiXk-Gjx59WiQvcTe46rXFrw@mail.gmail.com/T/#m67dce3408cac40318ae3dbe1c713b13621ac66c9
--
Siemens AG, Foundational Technologies
Linux Expert Center
next prev parent reply other threads:[~2025-02-21 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 22:07 Luis Claudio R. Goncalves
2025-02-21 9:50 ` Jan Kiszka [this message]
2025-02-24 13:29 ` Luis Claudio R. Goncalves
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=26f102f6-4e35-4267-b6ec-9ebd0c7572f7@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=daniel.wagner@suse.com \
--cc=jeffreyjbrady@gmail.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=pavel@denx.de \
--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
all inboxes | Powered by JetHome®