From: patchwork-bot+netdevbpf@kernel.org
To: Nicolai Buchwitz <nb@tipi-net.de>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux@armlinux.org.uk,
theo.lebrun@bootlin.com, conor.dooley@microchip.com,
atenart@kernel.org, o.rempel@pengutronix.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] net: macb: fix two probe path leaks
Date: Wed, 09 Sep 2026 01:40:05 +0000 [thread overview]
Message-ID: <178891800539.103980.5397686662404338366.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260907210856.1673589-1-nb@tipi-net.de>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 7 Sep 2026 23:08:54 +0200 you wrote:
> Two independent leaks on macb probe paths, both noticed while reviewing
> the fixed-link unbind crash fix [1].
>
> Patch 1 destroys the phylink instance when probe fails after
> macb_mii_init() has succeeded. Patch 2 drops the "mdio" child node
> reference on the success path of macb_mii_init().
>
> [...]
Here is the summary with links:
- [net,1/2] net: macb: destroy the phylink instance on the probe error path
https://git.kernel.org/netdev/net/c/7d059f390750
- [net,2/2] net: macb: put the "mdio" child node reference on success
https://git.kernel.org/netdev/net/c/382a373d9ea7
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:[~2026-09-09 1:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 21:08 [PATCH net 0/2] net: macb: fix two probe path leaks Nicolai Buchwitz
2026-09-07 21:08 ` [PATCH net 1/2] net: macb: destroy the phylink instance on the probe error path Nicolai Buchwitz
2026-09-07 21:08 ` [PATCH net 2/2] net: macb: put the "mdio" child node reference on success Nicolai Buchwitz
2026-09-09 1: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=178891800539.103980.5397686662404338366.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=atenart@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=theo.lebrun@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.