From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Ionut Nechita (Wind River)" <ionut.nechita@windriver.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org,
linux-serial <linux-serial@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
chris.friesen@windriver.com
Subject: Re: [REQUEST] Backport 8250_dw BUSY deassert series to 6.12.y stable
Date: Fri, 8 May 2026 20:13:30 +0300 (EEST) [thread overview]
Message-ID: <deb9499d-3245-7e38-9034-e533d4b5f512@linux.intel.com> (raw)
In-Reply-To: <20260508154629.530915-1-ionut.nechita@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 2333 bytes --]
On Fri, 8 May 2026, Ionut Nechita (Wind River) wrote:
> From: Ionut Nechita <ionut.nechita@windriver.com>
>
> Hi Greg,
>
> Fair question. We're shipping 6.12 as part of a certified platform
> (StarlingX/Yocto) that is already deployed in production at customer
> sites. A major kernel version bump requires a full re-qualification
> cycle across the entire platform stack (RT latency validation,
> out-of-tree driver compat, storage/networking regression testing),
> which is a multi-month effort we cannot justify for a single
> subsystem fix.
>
> We are planning the move to a newer LTS for our next major release,
> but for the current production branch 6.12 is what we're committed to.
>
> Since patch 7/7 already carries Cc: stable, would it be possible to
> pull in just the minimal dependencies needed to make it apply on
> 6.12.y? We're happy to do the backport work ourselves and submit it
> for review if that helps — we just wanted to check with Ilpo first
> on what the correct minimal subset would be before sending something
> that might be wrong.
Ah, this didn't get backported that far likely due to some syntax related
changes causing conflicts with the series.
To backport the entire series my suggestion is to take parts of the
commits:
dbd26a886e94 ("serial: 8250: use serial_port_in/out() helpers") (8250_dw.c only or just all if it goes cleanly)
b339809edda1 ("serial: 8250: use guard()s") (8250_port.c shutdown hunks)
And this completely (just syntax changes):
bd8cad85561b ("serial: 8250_dw: Comment possible corner cases in serial_out() implementation")
Those above are effectively just syntax changes but result in conflicts if
not applied prior to the BUSY fix series.
This leaves only minor conflicts in:
a7b9ce39fbe4 ("serial: 8250_dw: Ensure BUSY is deasserted")
with type change in
fc9ceb501e38 ("serial: 8250: sanitize uart_port::serial_{in,out}() types")
(trivial resolution as the change was in the code removed by the BUSY
change)
73a4ed8f9efa ("serial: 8250_dw: Rework IIR_NO_INT handling to stop interrupt storm")
with probe function changes (handle_irq assignment changes and unrelated
dw8250_setup_dma_filter() change) in
c213375e3283 ("serial: 8250_dw: Call dw8250_quirks() conditionally")
Hope this helps.
--
i.
prev parent reply other threads:[~2026-05-08 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 15:16 [REQUEST] Backport 8250_dw BUSY deassert series to 6.12.y stable Ionut Nechita (Wind River)
2026-05-08 15:21 ` Greg KH
2026-05-08 15:46 ` Ionut Nechita (Wind River)
2026-05-08 17:13 ` Ilpo Järvinen [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=deb9499d-3245-7e38-9034-e533d4b5f512@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chris.friesen@windriver.com \
--cc=gregkh@linuxfoundation.org \
--cc=ionut.nechita@windriver.com \
--cc=linux-serial@vger.kernel.org \
--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