[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025102230-omega-octopus-3cf1@gregkh>
Date: Wed, 22 Oct 2025 09:48:37 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Christoph Hellwig <hch@....de>
Cc: Gerd Bayer <gbayer@...ux.ibm.com>, Keith Busch <kbusch@...nel.org>,
Jens Axboe <axboe@...nel.dk>, Sagi Grimberg <sagi@...mberg.me>,
Niklas Schnelle <schnelle@...ux.ibm.com>,
linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] nvme-pci: Print error message on failure in
nvme_probe
On Wed, Oct 22, 2025 at 08:26:34AM +0200, Christoph Hellwig wrote:
> 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.
We have that already, dev_err_probe(), no need to create
yet-another-version of that.
thanks,
greg k-h
Powered by blists - more mailing lists