From: Pavel Machek <pavel@denx.de>
To: Clark Williams <williams@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Daniel Wagner <daniel.wagner@suse.com>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Pavel Machek <pavel@denx.de>,
Joseph Salisbury <joseph.salisbury@oracle.com>,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Subject: Re: [ANNOUNCE] 6.1.120-rt46
Date: Fri, 17 Jan 2025 12:13:22 +0100 [thread overview]
Message-ID: <Z4o7Usi2t3LFKwXC@duo.ucw.cz> (raw)
In-Reply-To: <173446426761.810839.10241405280484476684@demetrius>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
Hi!
>
> I'm pleased to announce the 6.1.120-rt46 stable release.
>
> 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: v6.1-rt
> Head SHA1: 061eae4897c2fee62fed3f946864107faf3292b7
>
> Or to build 6.1.120-rt46 directly, the following patches should be applied:
>
> https://www.kernel.org/pub/linux/kernel/v6.x/linux-6.1.tar.xz
>
> https://www.kernel.org/pub/linux/kernel/v6.x/patch-6.1.120.xz
>
> https://www.kernel.org/pub/linux/kernel/projects/rt/6.1/patch-6.1.120-rt46.patch.xz
Are there any plans for 6.1.124-based -rt? It would be useful for me
in context of -rt project.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2025-01-17 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 19:37 [ANNOUNCE] 6.1.120-rt46 Clark Williams
2024-12-27 15:23 ` 6.1.120-rt46 and build failure due to conflict with rebase against 34d21de99cea ("net: Move {l,t,d}stats allocation to core and convert veth & vrf") (was: Re: [ANNOUNCE] 6.1.120-rt46) Salvatore Bonaccorso
2025-01-17 11:13 ` Pavel Machek [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=Z4o7Usi2t3LFKwXC@duo.ucw.cz \
--to=pavel@denx.de \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=daniel.wagner@suse.com \
--cc=jkacur@redhat.com \
--cc=joseph.salisbury@oracle.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.