From: Sergey Ryazanov <ryazanov.s.a@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Alexander Aring" <alex.aring@gmail.com>,
"Stefan Schmidt" <stefan@datenfreihafen.org>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Loic Poulain" <loic.poulain@linaro.org>,
"Simon Horman" <horms@kernel.org>
Cc: Russell King <linux@armlinux.org.uk>,
Johannes Berg <johannes@sipsolutions.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 4/4] net: Switch back to struct platform_driver::remove()
Date: Fri, 4 Oct 2024 02:12:15 +0300 [thread overview]
Message-ID: <0d6070ef-d830-45e7-9162-edc025e459a1@gmail.com> (raw)
In-Reply-To: <3f7c05c8b7673c0bda3530c34bda5feee4843816.1727949050.git.u.kleine-koenig@baylibre.com>
On 03.10.2024 13:01, 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/net after the previous
> conversion commits apart from the wireless drivers 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>
> ---
> drivers/net/fjes/fjes_main.c | 2 +-
> drivers/net/ieee802154/fakelb.c | 2 +-
> drivers/net/ieee802154/mac802154_hwsim.c | 2 +-
> drivers/net/ipa/ipa_main.c | 2 +-
> drivers/net/pcs/pcs-rzn1-miic.c | 2 +-
> drivers/net/phy/sfp.c | 2 +-
> drivers/net/wan/framer/pef2256/pef2256.c | 2 +-
> drivers/net/wan/fsl_qmc_hdlc.c | 2 +-
> drivers/net/wan/fsl_ucc_hdlc.c | 2 +-
> drivers/net/wan/ixp4xx_hss.c | 2 +-
> drivers/net/wwan/qcom_bam_dmux.c | 2 +-
> 11 files changed, 11 insertions(+), 11 deletions(-)
For the WWAN patch,
Reviewed-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
next prev parent reply other threads:[~2024-10-03 23:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 10:01 [PATCH net-next v2 0/4] net: Switch back to struct platform_driver::remove() Uwe Kleine-König
2024-10-03 10:01 ` [PATCH net-next v2 1/4] net: ethernet: " Uwe Kleine-König
2024-10-03 10:01 ` [PATCH net-next v2 2/4] net: dsa: " Uwe Kleine-König
2024-10-03 13:11 ` Andrew Lunn
2024-10-03 10:01 ` [PATCH net-next v2 3/4] net: mdio: " Uwe Kleine-König
2024-10-03 13:12 ` Andrew Lunn
2024-10-03 10:01 ` [PATCH net-next v2 4/4] net: " Uwe Kleine-König
2024-10-03 13:13 ` Andrew Lunn
2024-10-03 23:12 ` Sergey Ryazanov [this message]
2024-10-04 7:38 ` Stefan Schmidt
2024-10-04 23:50 ` [PATCH net-next v2 0/4] " patchwork-bot+netdevbpf
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=0d6070ef-d830-45e7-9162-edc025e459a1@gmail.com \
--to=ryazanov.s.a@gmail.com \
--cc=alex.aring@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=loic.poulain@linaro.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan@datenfreihafen.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;
as well as URLs for NNTP newsgroup(s).