From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: Switch back to struct platform_driver::remove()
Date: Tue, 24 Sep 2024 11:00:34 +0200 [thread overview]
Message-ID: <2024092418-utensil-albatross-930c@gregkh> (raw)
In-Reply-To: <20240924084329.53094-2-u.kleine-koenig@baylibre.com>
On Tue, Sep 24, 2024 at 10:43:29AM +0200, Uwe Kleine-König wrote:
> After commit 0edb555a65d1 ("platform: Make platform_driver::remove()
> return void") .remove() is (again) the right callback to implement for
> platform drivers.
>
> Convert all platform drivers below drivers/usb to use .remove(), with
> the eventual goal to drop struct platform_driver::remove_new(). As
> .remove() and .remove_new() have the same prototypes, conversion is done
> by just changing the structure member name in the driver initializer.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>
> ---
> Hello Greg,
>
> given the simplicity of the individual changes I do this all in a single
> patch. Please tell and I will happily split it for an improved commit
> count :-) I based this on today's next, feel free to drop changes that
> result in a conflict when you come around to apply this. I'll care for
> the fallout at a later time then. (Having said that, if you use b4 am -3
> and git am -3, there should be hardly any fallout.)
>
> Note I didn't Cc: all the individual driver maintainers to not trigger
> sending limits and spam filters.
I'll take this after -rc1 is out, no worries. thanks for the patch!
greg k-h
prev parent reply other threads:[~2024-09-24 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 8:43 [PATCH] usb: Switch back to struct platform_driver::remove() Uwe Kleine-König
2024-09-24 9:00 ` Greg Kroah-Hartman [this message]
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=2024092418-utensil-albatross-930c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--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