From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Christian Eggers <ceggers@arri.de>,
linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RT] v6.12-rt stable branch?
Date: Thu, 9 Jan 2025 11:47:57 +0100 [thread overview]
Message-ID: <20250109104757.lszbnJUq@linutronix.de> (raw)
In-Reply-To: <20250109-sensation-diabetic-9b082008c6d4@thorsis.com>
On 2025-01-09 09:35:20 [+0100], Alexander Dahl wrote:
> Hei hei,
>
> Am Thu, Jan 09, 2025 at 09:23:23AM +0100 schrieb Christian Eggers:
> > Although most of the remaining RT stuff has been merged into linux-6.12, there
> > seems to be still no out-of-the box support for RT on ARM 32 bit platforms.
>
> This is also how I understood it.
I've been asking who needs ARM support and nobody spoke up. Arnd then
picked up some of the patches and for v6.13 the ARM queue got smaller.
Looking at what affects ARM from the queue there is just the ktimer
thread and the ARM specific bits. Lazy-preempt isn't implemented.
> > Are there any plans to release (and maintain) a v6.12-rt stable branch? Or shall
> > I pickup the necessary patches into my local branch myself?
>
> We have some systems with Microchip AT91 SoCs (SAMA5D2, SAM9X60) and I
> would be interested in those patches as well. The last patch
> published was 6.12-rc4-rt6 from october.
v6.12 is a LTS. And I wanted to add some PowerPC bits because it does
not boot on some parts as I've been told.
What about I make a release for the current stable tree and then update
it once the patches no longer apply on a newer stable tree?
> Greets
> Alex
Sebastian
next prev parent reply other threads:[~2025-01-09 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 8:23 [RT] v6.12-rt stable branch? Christian Eggers
2025-01-09 8:35 ` Alexander Dahl
2025-01-09 10:47 ` Sebastian Andrzej Siewior [this message]
2025-01-09 11:27 ` Christian Eggers
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=20250109104757.lszbnJUq@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=ceggers@arri.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.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