From: "Ionut Nechita (Wind River)" <ionut.nechita@windriver.com>
To: ilpo.jarvinen@linux.intel.com
Cc: adriana@arista.com, andriy.shevchenko@linux.intel.com,
chris.friesen@windriver.com, gregkh@linuxfoundation.org,
jirislaby@kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, qianfanguijin@163.com,
shankar.bandal@intel.com, shanth.murthy@intel.com
Subject: Re: [PATCH v4 0/7] 8250 DW UART fixes when under constant Rx pressure
Date: Fri, 6 Mar 2026 09:45:43 +0200 [thread overview]
Message-ID: <20260306074543.9953-1-ionut.nechita@windriver.com> (raw)
In-Reply-To: <20260203171049.4353-1-ilpo.jarvinen@linux.intel.com>
Hi Ilpo,
I've been looking at your patch series "[PATCH v4 0/7] 8250 DW UART fixes
when under constant Rx pressure" and I noticed it hasn't been picked up
in linux-next yet.
Could you please let me know if there is a newer revision of this series
beyond v4, and whether it has been merged upstream?
Thank you!
Best regards,
Ionut Nechita
prev parent reply other threads:[~2026-03-06 7:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 17:10 [PATCH v4 0/7] 8250 DW UART fixes when under constant Rx pressure Ilpo Järvinen
2026-02-03 17:10 ` [PATCH v4 1/7] serial: 8250: Protect LCR write in shutdown Ilpo Järvinen
2026-02-03 17:10 ` [PATCH v4 2/7] serial: 8250_dw: Avoid unnecessary LCR writes Ilpo Järvinen
2026-02-03 17:10 ` [PATCH v4 3/7] serial: 8250: Add serial8250_handle_irq_locked() Ilpo Järvinen
2026-02-03 17:10 ` [PATCH v4 4/7] serial: 8250_dw: Rework dw8250_handle_irq() locking and IIR handling Ilpo Järvinen
2026-02-03 17:10 ` [PATCH v4 5/7] serial: 8250_dw: Rework IIR_NO_INT handling to stop interrupt storm Ilpo Järvinen
2026-02-03 17:10 ` [PATCH v4 6/7] serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY Ilpo Järvinen
2026-02-03 17:10 ` [PATCH v4 7/7] serial: 8250_dw: Ensure BUSY is deasserted Ilpo Järvinen
2026-03-06 7:45 ` Ionut Nechita (Wind River) [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=20260306074543.9953-1-ionut.nechita@windriver.com \
--to=ionut.nechita@windriver.com \
--cc=adriana@arista.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chris.friesen@windriver.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=qianfanguijin@163.com \
--cc=shankar.bandal@intel.com \
--cc=shanth.murthy@intel.com \
/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