Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: stable@vger.kernel.org, Jan Kiszka <jan.kiszka@siemens.com>,
	Jon Humphreys <j-humphreys@ti.com>,
	Russell King <rmk+kernel@armlinux.org.uk>
Subject: Re: [PATCH v6.18 0/3] ARM: PREEMPT_RT backports
Date: Mon, 6 Jul 2026 11:27:33 +0200	[thread overview]
Message-ID: <2026070604-washday-tightrope-dcee@gregkh> (raw)
In-Reply-To: <20260706085940.3lUHUu8z@linutronix.de>

On Mon, Jul 06, 2026 at 10:59:40AM +0200, Sebastian Andrzej Siewior wrote:
> On 2026-07-02 16:06:48 [+0200], Greg KH wrote:
> > On Mon, Jun 29, 2026 at 04:41:28PM +0200, Sebastian Andrzej Siewior wrote:
> > > Hi,
> > > 
> > > ARM missed the PREEMPT_RT window for v6.18. The following three patches
> > > have been merged as of v7.1-rc1 and are the missing pieces.
> > > 
> > > I've been asked by people if it would be possible to include them in the
> > > stable tree as it would make their life easier.
> > 
> > Why can't the -rt patchset just include these?  Why put the burden on
> > us?
> 
> It is part of the -rt patchset. I've been asked if it would be possible
> to include it (ARM support) as part of -stable tree. I've been looking
> at what is missing and it included two Kconfig changes and one code
> change. This looked small so I thought maybe, why not let's ask. I'm
> sorry if it looked other than asking.
> 
> If this puts burden on you and it does not qualify for a stable change
> then it can't be included.

Please let's have new features stick to feature-patchsets like the -rt
kernel is, and not put that burden on us stable maintainers for
something that we don't use :)

thanks,

greg k-h

  reply	other threads:[~2026-07-06  9:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29 14:41 [PATCH v6.18 0/3] ARM: PREEMPT_RT backports Sebastian Andrzej Siewior
2026-06-29 14:41 ` [PATCH v6.18 1/3] ARM: 9459/1: Disable jump-label on PREEMPT_RT Sebastian Andrzej Siewior
2026-06-29 14:41 ` [PATCH v6.18 2/3] ARM: ensure interrupts are enabled in __do_user_fault() Sebastian Andrzej Siewior
2026-06-29 14:41 ` [PATCH v6.18 3/3] ARM: 9463/1: Allow to enable RT Sebastian Andrzej Siewior
2026-07-02 14:06 ` [PATCH v6.18 0/3] ARM: PREEMPT_RT backports Greg KH
2026-07-06  8:59   ` Sebastian Andrzej Siewior
2026-07-06  9:27     ` Greg KH [this message]
2026-07-06  9:30       ` 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=2026070604-washday-tightrope-dcee@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bigeasy@linutronix.de \
    --cc=j-humphreys@ti.com \
    --cc=jan.kiszka@siemens.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=stable@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