Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@meta.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me,
	Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH] nvme: use better description for async reset reason
Date: Fri, 23 Aug 2024 08:27:44 +0200	[thread overview]
Message-ID: <20240823062744.GA31687@lst.de> (raw)
In-Reply-To: <20240822152259.3896264-1-kbusch@meta.com>

On Thu, Aug 22, 2024 at 08:22:59AM -0700, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
> 
> The NVMe AER notification of a persistent internal error triggers a
> reset. The existing warning message just says "due to AER", which can be
> confused with the unlreated PCIe AER condition. Just say what the event
> was instead of the generic overloaded acronym.

Looks good:

Reviewed-by: Christoph Hellwig <hch@lst.de>



  reply	other threads:[~2024-08-23  6:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22 15:22 [PATCH] nvme: use better description for async reset reason Keith Busch
2024-08-23  6:27 ` Christoph Hellwig [this message]
2024-08-23  6:38 ` Chaitanya Kulkarni
2024-08-25  9:04 ` Sagi Grimberg

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=20240823062744.GA31687@lst.de \
    --to=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=kbusch@meta.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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