From: Gerd Bayer <gbayer@linux.ibm.com>
To: John Garry <john.g.garry@oracle.com>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Cc: Niklas Schnelle <schnelle@linux.ibm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Chaitanya Kulkarni <kch@nvidia.com>,
Wilfred Mallawa <wilfred.mallawa@wdc.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Chaitanya Kulkarni <kch@nvidia.com>
Subject: Re: [PATCH v2 2/2] nvme-pci: Add debug message on fail to read CSTS
Date: Thu, 23 Oct 2025 16:17:31 +0200 [thread overview]
Message-ID: <96c1a4e2bcf93d85b6ff33a30a045ebe7b29fb46.camel@linux.ibm.com> (raw)
In-Reply-To: <8d1d9153-810e-4e2b-804a-760bb3523e97@oracle.com>
On Thu, 2025-10-23 at 11:55 +0100, John Garry wrote:
> On 22/10/2025 11:33, Gerd Bayer wrote:
> > Add a debug log spelling out that reading the CSTS register failed - to
> > distinguish this from other reasons for ENODEV.
> >
> > Reviewed-by: Wilfred Mallawa <wilfred.mallawa@wdc.com>
> > Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
> > Signed-off-by: Gerd Bayer <gbayer@linux.ibm.com>
> > ---
> > drivers/nvme/host/pci.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
> > index 8c624960c9f67e0cc8409023de5e532d6ed9b3ac..ce563e93d29443a25e9236d0b6d8152ee85796d7 100644
> > --- a/drivers/nvme/host/pci.c
> > +++ b/drivers/nvme/host/pci.c
> > @@ -2906,6 +2906,7 @@ static int nvme_pci_enable(struct nvme_dev *dev)
> > pci_set_master(pdev);
> >
> > if (readl(dev->bar + NVME_REG_CSTS) == -1) {
> > + dev_dbg(dev->ctrl.device, "reading CSTS register failed");
>
> we should add "\n" as a good practice, no?
that's a very valid point. Sheesh - how much can go wrong...
Thanks,
Gerd
>
> > result = -ENODEV;
> > goto disable;
> > }
> >
prev parent reply other threads:[~2025-10-23 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 10:33 [PATCH v2 0/2] nvme-pci: Log failures to probe Gerd Bayer
2025-10-22 10:33 ` [PATCH v2 1/2] nvme-pci: Print error message on failure in nvme_probe Gerd Bayer
2025-10-22 10:53 ` Gerd Bayer
2025-10-23 8:13 ` Christoph Hellwig
2025-10-22 10:33 ` [PATCH v2 2/2] nvme-pci: Add debug message on fail to read CSTS Gerd Bayer
2025-10-23 8:13 ` Christoph Hellwig
2025-10-23 10:55 ` John Garry
2025-10-23 14:17 ` Gerd Bayer [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=96c1a4e2bcf93d85b6ff33a30a045ebe7b29fb46.camel@linux.ibm.com \
--to=gbayer@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=john.g.garry@oracle.com \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=schnelle@linux.ibm.com \
--cc=wilfred.mallawa@wdc.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;
as well as URLs for NNTP newsgroup(s).