[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251022062634.GA4790@lst.de>
Date: Wed, 22 Oct 2025 08:26:34 +0200
From: Christoph Hellwig <hch@....de>
To: Gerd Bayer <gbayer@...ux.ibm.com>
Cc: Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...nel.dk>,
Christoph Hellwig <hch@....de>, Sagi Grimberg <sagi@...mberg.me>,
Niklas Schnelle <schnelle@...ux.ibm.com>,
linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 1/2] nvme-pci: Print error message on failure in
nvme_probe
On Mon, Oct 20, 2025 at 05:29:07PM +0200, Gerd Bayer wrote:
> Add a new error message like
> nvme nvme0: probe failed on 2004:00:00.0 (result: -19)
> that makes failures to probe visible in the kernel log.
Is that really a thing drivers are expected to do? If it is generally
usefull I'd expect it to be in the driver core.
Also for nvme most "interesting" errors happen in the reset workqueue
and not in ->probe itself.
Powered by blists - more mailing lists