RealTime Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Stable RT List <stable-rt@vger.kernel.org>
Subject: Re: Question about the maintenance of OOT RT patches for LTS releases (v12.x and v18.x)
Date: Thu, 25 Jun 2026 10:02:27 +0200	[thread overview]
Message-ID: <20260625080227.WCsryMw4@linutronix.de> (raw)
In-Reply-To: <20260625-afar-trailside-f84c5025dc57@thorsis.com>

On 2026-06-25 09:35:19 [+0200], Alexander Dahl wrote:
> Hello,
> 
> just adding one datapoint here in case someone is wondering if there
> are users out there? ;-)

Sure. Having an update from _any_ user feels good. At least the work is
used ;)

> > Sebastian, just to make sure I understood your answer, then we don't need
> > to keep the OOT patches up-to-date for v6.18-rt specifically? My question
> > came from comments raised on the last two RT maintainers meetings and the
> > LF RT Board meeting. I just want to have a good answer if somebody else
> > asks about that. And to volunteer if work is needed.
> 
> We still use v6.12 LTS with PREEMPT_RT on arm32 (at91),
> and plan to use PREEMPT_RT on at91 (sam9x60, sama5d2) in the future.
> 
> If there are no regular patches for v6.18 we will probably skip that
> and use the LTS coming later this year.

I did assume we have v6.18 in maintenance but somehow it skipped. *I*
usually skip updates if there are no clashes and nothing changes.

> Greets
> Alex

Sebastian

  reply	other threads:[~2026-06-25  8:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-22 16:11 Question about the maintenance of OOT RT patches for LTS releases (v12.x and v18.x) Luis Claudio R. Goncalves
2026-06-24  6:49 ` Sebastian Andrzej Siewior
2026-06-24 11:14   ` Luis Claudio R. Goncalves
2026-06-25  7:35     ` Alexander Dahl
2026-06-25  8:02       ` Sebastian Andrzej Siewior [this message]
2026-06-25  7:52     ` 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=20260625080227.WCsryMw4@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=lgoncalv@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=stable-rt@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