[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220330042505.2902770-6-kuba@kernel.org>
Date: Tue, 29 Mar 2022 21:24:56 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: davem@...emloft.net
Cc: netdev@...r.kernel.org, pabeni@...hat.com, corbet@....net,
bpf@...r.kernel.org, linux-doc@...r.kernel.org, andrew@...n.ch,
f.fainelli@...il.com, Jakub Kicinski <kuba@...nel.org>
Subject: [PATCH net v3 05/14] docs: netdev: note that RFC postings are allowed any time
Document that RFCs are allowed during the merge window.
Signed-off-by: Jakub Kicinski <kuba@...nel.org>
Reviewed-by: Andrew Lunn <andrew@...n.ch>
Reviewed-by: Florian Fainelli <f.fainelli@...il.com>
---
v2: new patch
---
Documentation/networking/netdev-FAQ.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst
index 041993258dda..f4c77efa75d4 100644
--- a/Documentation/networking/netdev-FAQ.rst
+++ b/Documentation/networking/netdev-FAQ.rst
@@ -74,6 +74,9 @@ sent to netdev, but knowing the above, you can predict that in advance.
Do not send new ``net-next`` content to netdev during the
period during which ``net-next`` tree is closed.
+RFC patches sent for review only are obviously welcome at any time
+(use ``--subject-prefix='RFC net-next'`` with ``git format-patch``).
+
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)
release.
--
2.34.1
Powered by blists - more mailing lists