netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: patchwork-bot+netdevbpf@kernel.org
Cc: =?utf-8?b?QmVuY2UgQ3PDs2vDoXMgPGNzb2thcy5iZW5jZUBwcm9sYW4uaHU+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
	geert+renesas@glider.be, sergei.shtylyov@cogentembedded.com,
	davem@davemloft.net, robh@kernel.org, andrew@lunn.ch,
	andriy.shevchenko@linux.intel.com, dmitry.torokhov@gmail.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	buday.csaba@prolan.hu, hkallweit1@gmail.com, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net] net: mdio_bus: Use devm for getting reset GPIO
Date: Fri, 1 Aug 2025 13:34:57 +0100	[thread overview]
Message-ID: <aIy0cTjW1ETsY2NS@shell.armlinux.org.uk> (raw)
In-Reply-To: <175392840851.2582155.14607525521532592549.git-patchwork-notify@kernel.org>

On Thu, Jul 31, 2025 at 02:20:08AM +0000, patchwork-bot+netdevbpf@kernel.org wrote:
> Hello:
> 
> This patch was applied to netdev/net.git (main)
> by Jakub Kicinski <kuba@kernel.org>:
> 
> On Mon, 28 Jul 2025 17:34:55 +0200 you wrote:
> > Commit bafbdd527d56 ("phylib: Add device reset GPIO support") removed
> > devm_gpiod_get_optional() in favor of the non-devres managed
> > fwnode_get_named_gpiod(). When it was kind-of reverted by commit
> > 40ba6a12a548 ("net: mdio: switch to using gpiod_get_optional()"), the devm
> > functionality was not reinstated. Nor was the GPIO unclaimed on device
> > remove. This leads to the GPIO being claimed indefinitely, even when the
> > device and/or the driver gets removed.
> > 
> > [...]
> 
> Here is the summary with links:
>   - [net] net: mdio_bus: Use devm for getting reset GPIO
>     https://git.kernel.org/netdev/net/c/3b98c9352511

This needs to be reverted, it's an abuse of devm on a device that is
not being probed. Sorry, I don't have time to generate a patch.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2025-08-01 12:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 15:34 [PATCH net] net: mdio_bus: Use devm for getting reset GPIO Bence Csókás
2025-07-31  1:16 ` Jakub Kicinski
2025-07-31  1:20   ` Andrew Lunn
2025-08-07  8:12   ` Csókás Bence
2025-07-31  2:20 ` patchwork-bot+netdevbpf
2025-08-01 12:34   ` Russell King (Oracle) [this message]
2025-08-01 12:01 ` Mark Brown
2025-08-01 12:25   ` Geert Uytterhoeven
2025-08-01 12:33     ` Russell King (Oracle)
2025-08-01 13:04       ` Csókás Bence
2025-08-01 13:15         ` Russell King (Oracle)

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=aIy0cTjW1ETsY2NS@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc==?utf-8?b?QmVuY2UgQ3PDs2vDoXMgPGNzb2thcy5iZW5jZUBwcm9sYW4uaHU+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc=andrew@lunn.ch \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=buday.csaba@prolan.hu \
    --cc=davem@davemloft.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=edumazet@google.com \
    --cc=geert+renesas@glider.be \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=patchwork-bot+netdevbpf@kernel.org \
    --cc=robh@kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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).