From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Cc: 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 09:52:38 +0200 [thread overview]
Message-ID: <20260625075238.yBVVPwdL@linutronix.de> (raw)
In-Reply-To: <aju8K3aPXCWr7v7z@redhat.com>
On 2026-06-24 08:14:51 [-0300], Luis Claudio R. Goncalves wrote:
> 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
I did update v6.18 recently. I do think at the very least the 8250 bits
are important in case something goes wrong.
> 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.
There isn't a lot that clashes in v6.12 and it is even less in v6.18.
However the printk/ serial changes in v6.18 caused some fallout exactly
there.
Hopefully we get the 8250 bits by the end of the year including i915 and
then we have just powerpc left and that one sysfs file and we can call
it a day.
> Best,
> Luis
Sebastian
prev parent reply other threads:[~2026-06-25 7:52 UTC|newest]
Thread overview: 12+ 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
2026-08-19 16:30 ` Bryan Brattlof
2026-08-20 14:23 ` Sebastian Andrzej Siewior
2026-08-20 15:57 ` Luis Claudio R. Goncalves
2026-08-20 16:12 ` Sebastian Andrzej Siewior
2026-08-20 17:23 ` Luis Claudio R. Goncalves
2026-08-20 19:31 ` Bryan Brattlof
2026-06-25 7:52 ` Sebastian Andrzej Siewior [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=20260625075238.yBVVPwdL@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 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.