public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
	Ping-Ke Shih <pkshih@realtek.com>,
	Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: [PATCH v2 0/3] sdio: Use bus type function for shutdown
Date: Mon, 12 Jan 2026 16:46:56 +0100	[thread overview]
Message-ID: <cover.1768232321.git.u.kleine-koenig@baylibre.com> (raw)

Hello,

this series is part of an effort to get rid of the .shutdown() callback
(and .probe() and .remove()) in struct device_driver. Preparing that,
all sdio drivers that up to now use this callback are converted to a new
sdio specific shutdown callback.

v1 is available at https://lore.kernel.org/all/cover.1765968841.git.ukleinek@kernel.org.

Changes since v1:
 - Drop patch 2/4 which resulted in a build failure with CONFIG_PM=n

Patches #2 and #3 depend on the first patch, and with just the first
patch applied there is a runtime warning (emitted by the driver core in
driver_register()) for each unconverted driver. So it would be nice to
get the whole series in during a single merge window to not let users
face the warning.

Given that all drivers are in drivers/net/wireless I suggest to apply
the whole series via the wireless tree.

Best regards
Uwe

Uwe Kleine-König (3):
  sdio: Provide a bustype shutdown function
  wifi: rsi: sdio: Migrate to use sdio specific shutdown function
  wifi: rtw88: sdio: Migrate to use sdio specific shutdown function

 drivers/mmc/core/sdio_bus.c                   | 25 +++++++++++++++++++
 .../net/wireless/realtek/rtw88/rtw8723cs.c    |  2 +-
 .../net/wireless/realtek/rtw88/rtw8723ds.c    |  2 +-
 .../net/wireless/realtek/rtw88/rtw8821cs.c    |  2 +-
 .../net/wireless/realtek/rtw88/rtw8822bs.c    |  2 +-
 .../net/wireless/realtek/rtw88/rtw8822cs.c    |  2 +-
 drivers/net/wireless/realtek/rtw88/sdio.c     |  3 +--
 drivers/net/wireless/realtek/rtw88/sdio.h     |  2 +-
 drivers/net/wireless/rsi/rsi_91x_sdio.c       |  5 ++--
 include/linux/mmc/sdio_func.h                 |  1 +
 10 files changed, 35 insertions(+), 11 deletions(-)

base-commit: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
-- 
2.47.3

             reply	other threads:[~2026-01-12 15:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12 15:46 Uwe Kleine-König [this message]
2026-01-12 15:46 ` [PATCH v2 1/3] sdio: Provide a bustype shutdown function Uwe Kleine-König
2026-01-15  1:26   ` Shawn Lin
2026-01-15  8:23     ` Uwe Kleine-König
2026-01-19  9:16   ` Johannes Berg
2026-01-19 15:00   ` Ulf Hansson
2026-01-19 18:25     ` Uwe Kleine-König
2026-01-20 10:25       ` Ulf Hansson
2026-01-20 10:27   ` Ulf Hansson
2026-01-20 10:29     ` Johannes Berg
2026-01-12 15:46 ` [PATCH v2 2/3] wifi: rsi: sdio: Migrate to use sdio specific " Uwe Kleine-König
2026-01-12 15:46 ` [PATCH v2 3/3] wifi: rtw88: " Uwe Kleine-König
2026-01-13  0:29   ` Ping-Ke Shih
2026-01-12 15:51 ` [PATCH v2 0/3] sdio: Use bus type function for shutdown Johannes Berg
2026-01-13  0:31   ` Ping-Ke Shih

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.1768232321.git.u.kleine-koenig@baylibre.com \
    --to=u.kleine-koenig@baylibre.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=ulf.hansson@linaro.org \
    /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