Re: [PATCH net-next] net/sched: Add precise drop reason for pfifo_fast queue overflows

[Simon Horman <horms@kernel.org>]

On Mon, Jul 28, 2025 at 05:11:37PM +0800, fan.yu9@zte.com.cn wrote:
> > BTW, it seems net-next is closed, you may need to resend it after it is> re-open.>> Thanks.
> 
> Hi Cong,  
> Thank you for your review and the feedback!
> Could you kindly share how to track the status of the net-next merge window?
> Should I monitor the linux-netdev mailing list for announcements, or is there a specific schedule I can follow? 

Hi,

The merge-window opens when a new version of the Kernel is released, in
this case v6.16 was released yesterday. It remains open until the
subsequent rc1 release is made, in this case that will be v6.17-rc1. That
is typically two weeks after the merge-window opens.

You can observe the current Kernel release in a variety of ways,
including visiting https://www.kernel.org/

The timing of the merge window can be predicted with some accuracy by
following kernel rc releases: it usually occurs 1 week after an rc7
release. (If not, an rc8 release occurs, and the merge window will likely
open a week after that; and so on.)


net-next closes around the time that the merge-window opens.
But there is some variance in exactly when this occurs, due
to the schedules of the maintainers.

net-next re-opens around the time that the merge-window closes.
But again there is some variance.

The opening and closing of net-next is announced, with [ANN] in
the subject on the netdev mailing list.

https://lore.kernel.org/netdev/?q=ANN


There is some more information on this topic here:
https://docs.kernel.org/process/maintainer-netdev.html#development-cycle