public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: yunhui cui <cuiyunhui@bytedance.com>
Cc: arnd@arndb.de, andriy.shevchenko@linux.intel.com,
	benjamin.larsson@genexis.eu, heikki.krogerus@linux.intel.com,
	ilpo.jarvinen@linux.intel.com, jirislaby@kernel.org,
	jkeeping@inmusicbrands.com, john.ogness@linutronix.de,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	markus.mayer@linaro.org, matt.porter@linaro.org,
	namcao@linutronix.de, paulmck@kernel.org, pmladek@suse.com,
	schnelle@linux.ibm.com, sunilvl@ventanamicro.com,
	tim.kryger@linaro.org
Subject: Re: [PATCH v7 1/4] serial: 8250: fix panic due to PSLVERR
Date: Tue, 3 Jun 2025 06:21:15 +0200	[thread overview]
Message-ID: <2025060339-panhandle-grandkid-4574@gregkh> (raw)
In-Reply-To: <CAEEQ3wnEN0GVjmGTGoRa2eTGnKoQ2gp3okx8m_XcgiwMvGwzPg@mail.gmail.com>

On Tue, Jun 03, 2025 at 09:54:29AM +0800, yunhui cui wrote:
> Hi All,
> 
> Gentle ping. Any comments on this patchset?

My bot responded to you when you sent it a few days ago.  Please see
what it said then as to what is going on at the moment.


  reply	other threads:[~2025-06-03  4:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28  6:26 [PATCH v7 1/4] serial: 8250: fix panic due to PSLVERR Yunhui Cui
2025-05-28  6:26 ` [PATCH v7 2/4] serial: 8250: avoid potential PSLVERR issue Yunhui Cui
2025-05-28  6:26 ` [PATCH v7 3/4] serial: 8250_dw: assert port->lock is held in dw8250_force_idle() Yunhui Cui
2025-05-28  6:26 ` [PATCH v7 4/4] serial: 8250_dw: fix PSLVERR on RX_TIMEOUT Yunhui Cui
2025-06-06 10:41   ` Greg KH
2025-06-03  1:54 ` [PATCH v7 1/4] serial: 8250: fix panic due to PSLVERR yunhui cui
2025-06-03  4:21   ` Greg KH [this message]
2025-06-06 10:40 ` Greg KH
2025-06-09  7:02   ` [External] " yunhui cui

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=2025060339-panhandle-grandkid-4574@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=benjamin.larsson@genexis.eu \
    --cc=cuiyunhui@bytedance.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jirislaby@kernel.org \
    --cc=jkeeping@inmusicbrands.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=markus.mayer@linaro.org \
    --cc=matt.porter@linaro.org \
    --cc=namcao@linutronix.de \
    --cc=paulmck@kernel.org \
    --cc=pmladek@suse.com \
    --cc=schnelle@linux.ibm.com \
    --cc=sunilvl@ventanamicro.com \
    --cc=tim.kryger@linaro.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