Please read
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
in this case 'don’t repost your patches within one 24h period'
Because:
- you have two patches now processing and no changes requested yet,
nor did you get AI review that is currently employed
https://patchwork.kernel.org/project/netdevbpf/patch/20260707195425.405989-1-stefan@agner.ch/
and
https://patchwork.kernel.org/project/netdevbpf/patch/20260707162146.73823-1-stefan@agner.ch/
- This change is actually broken - in previous patch rtnl_lock() was asserted
by dev_ioctl(), but in this version it is not asserted anywhere and will
trigger WARN_ONCE().
- Full tests within an hour is possible, but no need to rush patches
- Please spend time reviewing patches, as I spent few minutes to make sure
you (or rather Fable AI) is correct that rtnl_lock() was asserted, so my
review would be accurate (previous patch was ok, this is not).
- Please respond yourself to comments, take time to understand codebase.
I would prefer not getting copy-paste answer from AI,
we have Sashiko review for that.
- Missing link to previous thread, shown below
- Moving code to other lines does not justify dropping "Assisted by AI"
I am not maintainer, just random reviewer. Some maintainer will give input
surely soon.
But rule of thumb, do not repost patches till your patch gets
'Changes requested' in patchwork or like 2 weeks have passed
(maybe during vacation even longer, as currently there are >600 patches
pending review).
On Tue, Jul 07, 2026 at 09:54:25PM +0200, Stefan Agner wrote:
Changes in v2:
- Move the PHY resume from stmmac_change_mtu() into __stmmac_open() so
that it also counters the PHY suspend caused by __stmmac_release()
(suggested by Andrew Lunn), placed before stmmac_reset_queues_param()
to match the ordering used in stmmac_resume()
Missing link to previous thread
drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 9 +++++++++
1 file changed, 9 insertions(+)
BR
Jakub Raczynski