diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2026-03-06 17:48:03 -0800 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-03-06 17:48:03 -0800 |
| commit | 7a4d74676c31951c28b1df3dce4769d3acfb8e96 (patch) | |
| tree | 7369b9c60ee26ecfb5d17d1515e76bfdcb30f9ea /tools/perf/scripts/python | |
| parent | 0cc0c2e661af418bbf7074179ea5cfffc0a5c466 (diff) | |
| parent | ce2da643f00af3111f1fffe2adea8506592ef6e5 (diff) | |
| download | linux-7a4d74676c31951c28b1df3dce4769d3acfb8e96.tar.gz linux-7a4d74676c31951c28b1df3dce4769d3acfb8e96.zip | |
Merge branch 'further-sja1105-phylink-link-replay-fixups'
Vladimir Oltean says:
====================
Further SJA1105 phylink link replay fixups
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.
I haven't noticed any physical issues, it only has to do with the
soundness of the new call path introduced in January in commit
0b2edc531e0b ("net: dsa: sja1105: let phylink help with the replay of
link callbacks").
====================
Link: https://patch.msgid.link/20260304220900.3865120-1-vladimir.oltean@nxp.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions