From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
linux@armlinux.org.uk
Subject: Re: [PATCH net 0/2] Further SJA1105 phylink link replay fixups
Date: Sat, 07 Mar 2026 02:00:09 +0000 [thread overview]
Message-ID: <177284880980.123899.682744620861454371.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260304220900.3865120-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 5 Mar 2026 00:08:58 +0200 you wrote:
> While I was playing around with the subsystem knowledge in Chris Mason's
> review-prompts to see what LLMs would have needed to catch the bug
> behind commit bfd264fbbbca ("net: dsa: sja1105: protect link replay
> helpers against NULL phylink instance"), it flagged another issue
> instead, which IMO is valid. This is being fixed in patch 2/2.
> Patch 1/2 is preparatory reordering for that.
>
> [...]
Here is the summary with links:
- [net,1/2] net: dsa: sja1105: reorder sja1105_reload_cbs() and phylink_replay_link_end()
https://git.kernel.org/netdev/net/c/976703cae737
- [net,2/2] net: dsa: sja1105: ensure phylink_replay_link_end() will not be missed
https://git.kernel.org/netdev/net/c/ce2da643f00a
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-03-07 2:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 22:08 [PATCH net 0/2] Further SJA1105 phylink link replay fixups Vladimir Oltean
2026-03-04 22:08 ` [PATCH net 1/2] net: dsa: sja1105: reorder sja1105_reload_cbs() and phylink_replay_link_end() Vladimir Oltean
2026-03-04 22:09 ` [PATCH net 2/2] net: dsa: sja1105: ensure phylink_replay_link_end() will not be missed Vladimir Oltean
2026-03-07 2: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=177284880980.123899.682744620861454371.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.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