On Sat, Mar 26, 2022 at 07:53:51PM -0700, Jakub Kicinski wrote:
> Use the sphinx Warning box to make the net-next being closed
> stand out more.
>
> Signed-off-by: Jakub Kicinski <kuba@xxxxxxxxxx>
> ---
> Documentation/networking/netdev-FAQ.rst | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst
> index 0bff899f286f..c1683ed1faca 100644
> --- a/Documentation/networking/netdev-FAQ.rst
> +++ b/Documentation/networking/netdev-FAQ.rst
> @@ -73,8 +73,9 @@ relating to vX.Y
> An announcement indicating when ``net-next`` has been closed is usually
> sent to netdev, but knowing the above, you can predict that in advance.
>
> -IMPORTANT: Do not send new ``net-next`` content to netdev during the
> -period during which ``net-next`` tree is closed.
> +.. warning::
> + Do not send new ``net-next`` content to netdev during the
> + period during which ``net-next`` tree is closed.
>
> Shortly after the two weeks have passed (and vX.Y-rc1 is released), the
> tree for ``net-next`` reopens to collect content for the next (vX.Y+1)
Maybe somewhere around here mention that RFC patches can be posted
while net-next is closed? It is something we keep telling people, so
probably should be a FAQ item.
Andrew
