From: patchwork-bot+netdevbpf@kernel.org
To: Hongyan Xu <getshell@seu.edu.cn>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, jianhao.xu@seu.edu.cn
Subject: Re: [PATCH net-next v4] net: phy: nxp-tja11xx: cancel registration work on remove
Date: Thu, 06 Aug 2026 01:00:11 +0000 [thread overview]
Message-ID: <178597801163.587098.12117115424912791664.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260801140643.1871-1-getshell@seu.edu.cn>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 1 Aug 2026 22:06:43 +0800 you wrote:
> tja1102_p0_probe() schedules work to register the second port. That work
> uses the Port 0 private data and phydev. The private data is
> devm-allocated, but the driver does not wait for the pending work on
> remove.
>
> Store the Port 0 private data in phydev->priv and add a remove callback.
> The callback cancels the registration work before devres teardown frees
> the state.
>
> [...]
Here is the summary with links:
- [net-next,v4] net: phy: nxp-tja11xx: cancel registration work on remove
https://git.kernel.org/netdev/net-next/c/1aae367b1646
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-08-06 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 14:06 [PATCH net-next v4] net: phy: nxp-tja11xx: cancel registration work on remove Hongyan Xu
2026-08-06 1:00 ` 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=178597801163.587098.12117115424912791664.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=getshell@seu.edu.cn \
--cc=hkallweit1@gmail.com \
--cc=jianhao.xu@seu.edu.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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