From: Heiner Kallweit <hkallweit1@gmail.com>
To: Rosen Penev <rosenp@gmail.com>, netdev@vger.kernel.org
Cc: "Rafał Miłecki" <rafal@milecki.pl>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2 net-next] net: bgmac: use devm for register_netdev
Date: Mon, 14 Oct 2024 00:09:00 +0200 [thread overview]
Message-ID: <c7176768-1999-4167-b657-3afba97b81b7@gmail.com> (raw)
In-Reply-To: <20241013213400.9627-1-rosenp@gmail.com>
On 13.10.2024 23:34, Rosen Penev wrote:
> Removes need to unregister in _remove.
>
> Tested on ASUS RT-N16. No change in behavior.
>
This patch changes the order of calls. unregister_netdev() is now called
only after remove(). Shouldn't there be some words about why this is safe
and doesn't e.g. possibly result in race windows?
> Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
> Tested-by: Florian Fainelli <florian.fainelli@broadcom.com>
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
> v2: added reviewed/tested-by broadcom.
> drivers/net/ethernet/broadcom/bgmac.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/broadcom/bgmac.c b/drivers/net/ethernet/broadcom/bgmac.c
> index 6ffdc4229407..2599ffe46e27 100644
> --- a/drivers/net/ethernet/broadcom/bgmac.c
> +++ b/drivers/net/ethernet/broadcom/bgmac.c
> @@ -1546,7 +1546,7 @@ int bgmac_enet_probe(struct bgmac *bgmac)
>
> bgmac->in_init = false;
>
> - err = register_netdev(bgmac->net_dev);
> + err = devm_register_netdev(bgmac->dev, bgmac->net_dev);
> if (err) {
> dev_err(bgmac->dev, "Cannot register net device\n");
> goto err_phy_disconnect;
> @@ -1568,7 +1568,6 @@ EXPORT_SYMBOL_GPL(bgmac_enet_probe);
>
> void bgmac_enet_remove(struct bgmac *bgmac)
> {
> - unregister_netdev(bgmac->net_dev);
> phy_disconnect(bgmac->net_dev->phydev);
> netif_napi_del(&bgmac->napi);
> bgmac_dma_free(bgmac);
prev parent reply other threads:[~2024-10-13 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 21:34 [PATCHv2 net-next] net: bgmac: use devm for register_netdev Rosen Penev
2024-10-13 22:09 ` Heiner Kallweit [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=c7176768-1999-4167-b657-3afba97b81b7@gmail.com \
--to=hkallweit1@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rafal@milecki.pl \
--cc=rosenp@gmail.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