Linux MultiMedia Card development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
	"Ulf Hansson" <ulf.hansson@linaro.org>,
	"Ping-Ke Shih" <pkshih@realtek.com>
Cc: linux-wireless@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Re: [PATCH v2 1/3] sdio: Provide a bustype shutdown function
Date: Mon, 19 Jan 2026 10:16:35 +0100	[thread overview]
Message-ID: <0a7ae8fb2ccd37ff64d6f45089e46ff3f95fcc67.camel@sipsolutions.net> (raw)
In-Reply-To: <397f45c2818f6632151f92b70e547262f373c3b6.1768232321.git.u.kleine-koenig@baylibre.com> (sfid-20260112_164714_040401_1B7336B9)

On Mon, 2026-01-12 at 16:46 +0100, Uwe Kleine-König wrote:
> To prepare sdio drivers to migrate away from struct device_driver::shutdown
> (and then eventually remove that callback) create a serdev driver shutdown
> callback and migration code to keep the existing behaviour. Note this
> introduces a warning for each driver that isn't converted yet to that
> callback at register time.
> 
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>

Ulf, could you send an ACK for taking this through wireless?

Thanks,
johannes

  parent reply	other threads:[~2026-01-19  9:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12 15:46 [PATCH v2 0/3] sdio: Use bus type function for shutdown Uwe Kleine-König
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 [this message]
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: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=0a7ae8fb2ccd37ff64d6f45089e46ff3f95fcc67.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=u.kleine-koenig@baylibre.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