All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Bryan Brattlof <bb@ti.com>, Steven Rostedt <rostedt@goodmis.org>,
	Stable RT List <stable-rt@vger.kernel.org>,
	Praneeth Bajjuri <praneeth@ti.com>
Subject: Re: Question about the maintenance of OOT RT patches for LTS releases (v12.x and v18.x)
Date: Thu, 20 Aug 2026 12:57:47 -0300	[thread overview]
Message-ID: <aocj-6A2vEPw-5-O@redhat.com> (raw)
In-Reply-To: <20260820142314.OrEinRQt@linutronix.de>

On Thu, Aug 20, 2026 at 04:23:14PM +0200, Sebastian Andrzej Siewior wrote:
> On 2026-08-19 11:30:11 [-0500], Bryan Brattlof wrote:
> > > 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.
> > 
> > Did we decide to skip v6.18 ? There are a few people internally asking 
> > me for a roadmap again with some guidance on the lifetime of the branch.
> 
> As of v6.18.45 the v6.18.37-rt6 applies as-is. Winthin the git tree, the
> stable tree tag can be merged. Does this work?

There seems to be a conflict when applying the 8250 nbcon patches. IIRC you
fixed that conflict (or something quite close to that) on v7.1-rc.

The conflict:

$ git checkout -b test01 v6.18.37-rt6
$ git rebase -v v6.18.45
  Changes from 0c503cf3dde2e53614f05261ece12f9d3d4c3c20 to bf3be28f6721e24961992ebb9e61c0cf21a56806:
  ...
  Rebasing (1/29)
  dropping bea58d7ab5ba4367a3208ecd1854a74b66b21f51 net: gro_cells: fix lock imbalance in gro_cells_receive() -- patch contents already upstream
  Rebasing (2/29)
  Auto-merging drivers/tty/serial/8250/8250_port.c
  CONFLICT (content): Merge conflict in drivers/tty/serial/8250/8250_port.c
  Auto-merging include/linux/serial_8250.h
  error: could not apply 0b053910fa95... Reapply "serial: 8250: Switch to nbcon console"

Bryan, is this the problem you are seeing?

Luis

> 
> > ~Bryan
> 
> Sebastian
> 
---end quoted text---


  reply	other threads:[~2026-08-20 15:58 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 [this message]
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

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=aocj-6A2vEPw-5-O@redhat.com \
    --to=lgoncalv@redhat.com \
    --cc=bb@ti.com \
    --cc=bigeasy@linutronix.de \
    --cc=praneeth@ti.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.