From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Kai Mäkisara" <Kai.Makisara@kolumbus.fi>
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
Bart Van Assche <bvanassche@acm.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Peter Wang <peter.wang@mediatek.com>,
Bean Huo <beanhuo@micron.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Christoph Hellwig <hch@infradead.org>,
"Bao D. Nguyen" <quic_nguyenb@quicinc.com>,
linux-scsi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: [PATCH v2 0/8] scsi: Make use of bus callbacks
Date: Fri, 19 Dec 2025 10:25:29 +0100 [thread overview]
Message-ID: <cover.1766133330.git.u.kleine-koenig@baylibre.com> (raw)
Hello,
this is v2 of the series to make the scsi subsystem stop using the
callbacks .probe(), .remove() and .shutdown() of struct device_driver.
Instead use their designated alternatives in struct bus_type.
The eventual goal is to drop the callbacks from struct device_driver.
The 2nd patch introduces some legacy handling for drivers still using
the device_driver callbacks. This results in a runtime warning (in
driver_register()). The following patches convert all in-tree drivers
(and thus fix the warnings one after another).
Conceptually this legacy handling could be dropped at the end of the
series, but I think this is a bad idea because this silently breaks
out-of-tree drivers (which also covers drivers that are currently
prepared for mainline submission) and in-tree drivers I might have
missed (though I'm convinced I catched them all). That convinces me that
keeping the legacy handling for at least one development cycle is the
right choice. I'll care for that at the latest when I remove the
callbacks from struct device_driver.
Changes since (implicit) v1, available at
https://lore.kernel.org/linux-scsi/cover.1765312062.git.u.kleine-koenig@baylibre.com:
- trivially rebase to v6.19-rc1
- fix a kdoc warning uncovered by the intel kernel test robot
- rename a few variables to align with the already existing naming in
the individual drivers
- slightly reword the commit logs
- add the tags received in v1
Best regards
Uwe
Uwe Kleine-König (8):
scsi: Pass a struct scsi_driver to scsi_{,un}register_driver()
scsi: Make use of bus callbacks
scsi: ch: Convert to scsi bus methods
scsi: sd: Convert to scsi bus methods
scsi: ses: Convert to scsi bus methods
scsi: sr: Convert to scsi bus methods
scsi: st: Convert to scsi bus methods
scsi: ufs: Convert to scsi bus methods
drivers/scsi/ch.c | 18 ++++-----
drivers/scsi/scsi_sysfs.c | 77 ++++++++++++++++++++++++++++++++++++--
drivers/scsi/sd.c | 29 +++++++-------
drivers/scsi/ses.c | 15 ++------
drivers/scsi/sr.c | 21 +++++------
drivers/scsi/st.c | 22 +++++------
drivers/ufs/core/ufshcd.c | 22 +++++------
include/scsi/scsi_driver.h | 7 +++-
8 files changed, 139 insertions(+), 72 deletions(-)
base-commit: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
--
2.47.3
next reply other threads:[~2025-12-19 9:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 9:25 Uwe Kleine-König [this message]
2025-12-19 9:25 ` [PATCH v2 1/8] scsi: Pass a struct scsi_driver to scsi_{,un}register_driver() Uwe Kleine-König
2025-12-19 9:25 ` [PATCH v2 2/8] scsi: Make use of bus callbacks Uwe Kleine-König
2025-12-19 18:18 ` Bart Van Assche
2025-12-22 8:28 ` Peter Wang (王信友)
2025-12-19 9:25 ` [PATCH v2 8/8] scsi: ufs: Convert to scsi bus methods Uwe Kleine-König
2025-12-19 18:16 ` [PATCH v2 0/8] scsi: Make use of bus callbacks Bart Van Assche
2026-01-12 2:34 ` Martin K. Petersen
2026-01-17 4:36 ` Martin K. Petersen
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=cover.1766133330.git.u.kleine-koenig@baylibre.com \
--to=u.kleine-koenig@baylibre.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Kai.Makisara@kolumbus.fi \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=hch@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=peter.wang@mediatek.com \
--cc=quic_nguyenb@quicinc.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