From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?Q3PDs2vDoXMgQmVuY2UgPGNzb2thcy5iZW5jZUBwcm9sYW4uaHU+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: robh@kernel.org, geert+renesas@glider.be, davem@davemloft.net,
sergei.shtylyov@cogentembedded.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, buday.csaba@prolan.hu,
andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net v2] net: mdiobus: release reset_gpio in mdiobus_unregister_device()
Date: Tue, 12 Aug 2025 10:40:08 +0000 [thread overview]
Message-ID: <175499520897.2526251.3672901808475265988.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250807135449.254254-2-csokas.bence@prolan.hu>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 7 Aug 2025 15:54:49 +0200 you wrote:
> From: Buday Csaba <buday.csaba@prolan.hu>
>
> reset_gpio is claimed in mdiobus_register_device(), but it is not
> released in mdiobus_unregister_device(). It is instead only
> released when the whole MDIO bus is unregistered.
> When a device uses the reset_gpio property, it becomes impossible
> to unregister it and register it again, because the GPIO remains
> claimed.
> This patch resolves that issue.
>
> [...]
Here is the summary with links:
- [net,v2] net: mdiobus: release reset_gpio in mdiobus_unregister_device()
https://git.kernel.org/netdev/net/c/8ea25274ebaf
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-08-12 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 13:54 Bence Csókás
2025-08-12 10:40 ` patchwork-bot+netdevbpf [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=175499520897.2526251.3672901808475265988.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?Q3PDs2vDoXMgQmVuY2UgPGNzb2thcy5iZW5jZUBwcm9sYW4uaHU+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=andrew@lunn.ch \
--cc=buday.csaba@prolan.hu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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
all inboxes | Powered by JetHome®