Re: [PATCH net 0/6][pull request] Intel Wired LAN Driver Updates 2026-11-13 (ice)

From
Petr Oros <hidden>
Date
2026-11-18 11:59:40
Also in
intel-wired-lan
Reply to
Tony Nguyen, 2026-11-13
I think this pull is a good moment to ask how fixes for Intel drivers
should flow, because it is not the first time a fix spent months on
intel-wired-lan and then hit a wall on net.

My patches 2/6 and 3/6 have been on intel-wired-lan since June, v4 on
July 8 [1]. They were reviewed and tested by Intel validation there,
and four months later Sashiko found real problems in them on this
pull. I have a v5 and will send it once it is tested.

Jake's E82x timestamp fixes went through three pulls before a part of
them was applied [2], and Maciej described the same loop on the i40e
pull in September [3].

I know Intel patches go through iwl and are not applied to net
directly [4]. But for fixes it means that the review which decides
happens on netdev months after the iwl review and validation, and every
respin goes through both again. And if iwl stops cross-posting to
netdev, as Jakub suggested [5], Sashiko will see Intel fixes only in
the pull.

So does the iwl round still make sense for fixes? Would it be better to
send fixes straight to net with iwl in Cc, and have Tony's ack and the
Tested-by from Intel validation on netdev?

[1] https://lore.kernel.org/all/20260708125755.706263-1-poros@redhat.com/ (local)
[2] https://lore.kernel.org/all/20261021-jk-e825c-timestamp-processing-logic-fixes-srcu-v5-0-72289a4ac8eb@intel.com/ (local)
[3] https://lore.kernel.org/all/are4rBUJO3mzrkO8@boxer/ (local)
[4] https://lore.kernel.org/all/20260721174642.7749143e@kernel.org/ (local)
[5] https://lore.kernel.org/all/20260922112216.41e6f8cf@kernel.org/ (local)

Regards,
Petr
Thread (17 messages) 17 messages, 6 authors, last reply 4h ago
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help