Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Xia Yan <yanxia@cmss.chinamobile.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch, kuba@kernel.org,
	pabeni@redhat.com, edumazet@kernel.org, davem@davemloft.net,
	alexandru.tachici@analog.com, ciprian.regus@analog.com,
	linux-kernel@vger.kernel.org, yana06070@163.com
Subject: Re: [PATCH net-next] net: ethernet: adi: adin1110: Fix phy_device leak in probe_netdevs()
Date: Thu, 12 Nov 2026 11:30:10 +0000	[thread overview]
Message-ID: <179448301067.2033939.14773001196867592120.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1793949783000.333861.5224091507677300156@cmss.chinamobile.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri, 06 Nov 2026 15:23:03 +0800 you wrote:
> adin1110_probe_netdevs() probes each port with get_phy_device(), which
> allocates a phy_device without registering it. The pointer's only use
> is phydev_name() for the phy_connect() call, and phy_connect() attaches
> the device the earlier bus scan registered, not the one allocated here.
> port_priv->phydev is then overwritten with the phy_connect() result and
> the allocated object is lost.
> 
> [...]

Here is the summary with links:
  - [net-next] net: ethernet: adi: adin1110: Fix phy_device leak in probe_netdevs()
    https://git.kernel.org/netdev/net-next/c/acdf2d09fa18

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-12 11:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06  7:23 [PATCH net-next] net: ethernet: adi: adin1110: Fix phy_device leak in probe_netdevs() Xia Yan
2026-11-06  7:27 ` netdev-bot+sinfo
2026-11-06  7:53   ` Xia Yan
2026-11-12 11:30 ` 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=179448301067.2033939.14773001196867592120.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexandru.tachici@analog.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=ciprian.regus@analog.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=yana06070@163.com \
    --cc=yanxia@cmss.chinamobile.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