From: Bart Van Assche <bvanassche@acm.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/8] scsi: Make use of bus callbacks
Date: Tue, 9 Dec 2025 13:00:03 -0800 [thread overview]
Message-ID: <818c2c48-6962-46bb-8268-d377eaed3083@acm.org> (raw)
In-Reply-To: <59b408f6d89d402457a23564302afcbb334bc9dd.1765312062.git.u.kleine-koenig@baylibre.com>
On 12/9/25 12:45 PM, Uwe Kleine-König wrote:
> The objective is to get rid of users of struct device_driver callbacks
> .probe(), .remove() and .shutdown() to eventually remove these. Until
> all scsi drivers are converted this results in a runtime warning about
> the drivers needing an update because there is a bus probe function and
> a driver probe function. The in-tree drivers are fixed by the following
> commits.
Which runtime warning? Has that runtime warning perhaps been introduced
by a patch series that has not yet been merged?
Thanks,
Bart.
next prev parent reply other threads:[~2025-12-09 21:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 20:45 [PATCH 0/8] scsi: Make use of bus callbacks Uwe Kleine-König
2025-12-09 20:45 ` [PATCH 1/8] scsi: Pass a struct scsi_driver to scsi_{,un}register_driver() Uwe Kleine-König
2025-12-10 13:14 ` Peter Wang (王信友)
2025-12-09 20:45 ` [PATCH 2/8] scsi: Make use of bus callbacks Uwe Kleine-König
2025-12-09 20:59 ` Bart Van Assche
2025-12-09 21:22 ` Uwe Kleine-König
2025-12-10 5:26 ` Christoph Hellwig
2025-12-10 6:56 ` Uwe Kleine-König
2025-12-10 7:04 ` Christoph Hellwig
2025-12-10 10:34 ` Uwe Kleine-König
2025-12-09 21:00 ` Bart Van Assche [this message]
2025-12-09 21:26 ` Uwe Kleine-König
2025-12-09 20:45 ` [PATCH 3/8] scsi: ch: Convert to scsi bus methods Uwe Kleine-König
2025-12-09 20:45 ` [PATCH 4/8] scsi: sd: " Uwe Kleine-König
2025-12-10 9:20 ` kernel test robot
2025-12-10 9:50 ` Uwe Kleine-König
2025-12-15 4:10 ` kernel test robot
2025-12-09 20:45 ` [PATCH 5/8] scsi: ses: " Uwe Kleine-König
2025-12-09 20:45 ` [PATCH 6/8] scsi: sr: " Uwe Kleine-König
2025-12-09 20:45 ` [PATCH 7/8] scsi: st: " Uwe Kleine-König
2025-12-09 20:45 ` [PATCH 8/8] scsi: ufs: " Uwe Kleine-König
2025-12-10 13:14 ` Peter Wang (王信友)
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=818c2c48-6962-46bb-8268-d377eaed3083@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=u.kleine-koenig@baylibre.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