[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4be8e875-d8a0-4f3c-8305-5b0787039826@lunn.ch>
Date: Fri, 15 Aug 2025 06:07:27 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Yibo Dong <dong100@...se.com>
Cc: andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, horms@...nel.org,
corbet@....net, gur.stavi@...wei.com, maddy@...ux.ibm.com,
mpe@...erman.id.au, danishanwar@...com, lee@...ger.us,
gongfan1@...wei.com, lorenzo@...nel.org, geert+renesas@...der.be,
Parthiban.Veerasooran@...rochip.com, lukas.bulwahn@...hat.com,
alexanderduyck@...com, richardcochran@...il.com,
netdev@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 3/5] net: rnpgbe: Add basic mbx ops support
> By the way, how long should I wait before sending the new version? If it
> is too frequent, it might cause reviewers to check old versions and miss
> feedback, link what happened with this mail. And if it is too long, it
> is easy to miss the 'open window'....
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
Says at least 24 hours.
But i have been away from emails for a few days, so i was slower than
usual.
Most patches get reviewed in 3 work days. So i would probably not wait
much longer than that. But also wait for any discussion about a patch
to come to an end.
Also, different subsystems work are different speed. 3 days would be
way to fast for USB for example, that would be more like 2 weeks.
Andrew
Powered by blists - more mailing lists