[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <db8fce479c6a682d7ca1c37f7427ad30673fc34e.camel@linux.ibm.com>
Date: Wed, 22 Oct 2025 12:53:52 +0200
From: Gerd Bayer <gbayer@...ux.ibm.com>
To: Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...nel.dk>,
Christoph
Hellwig <hch@....de>, Sagi Grimberg <sagi@...mberg.me>
Cc: Niklas Schnelle <schnelle@...ux.ibm.com>,
Greg Kroah-Hartman
<gregkh@...uxfoundation.org>,
Chaitanya Kulkarni <kch@...dia.com>,
Wilfred
Mallawa <wilfred.mallawa@....com>,
linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] nvme-pci: Print error message on failure in
nvme_probe
On Wed, 2025-10-22 at 12:33 +0200, Gerd Bayer wrote:
> Add a new error message that makes failures to probe visible in the
> kernel log, like:
> nvme 0008:00:00.0: error -ENODEV: probe failed
>
> This highlights issues with a particular device right away instead of
> leaving users to search for missing drives.
>
> Signed-off-by: Gerd Bayer <gbayer@...ux.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 c916176bd9f058b49e6e6768675711df52b15765..8c624960c9f67e0cc8409023de5e532d6ed9b3ac 100644
> --- a/drivers/nvme/host/pci.c
> +++ b/drivers/nvme/host/pci.c
> @@ -3522,6 +3522,7 @@ static int nvme_probe(struct pci_dev *pdev, const struct pci_device_id *id)
> nvme_uninit_ctrl(&dev->ctrl);
> out_put_ctrl:
> nvme_put_ctrl(&dev->ctrl);
> + dev_err_probe(&pdev->dev, result, "probe failed\n");
> return result;
> }
This one failed to reach Chaitanya due to a typo in the email address
on my side. Sorry!
Powered by blists - more mailing lists