diff options
author | Jakub Kicinski <kuba@kernel.org> | 2022-03-29 21:24:56 -0700 |
---|---|---|
committer | Paolo Abeni <pabeni@redhat.com> | 2022-03-31 10:49:38 +0200 |
commit | 0e242e3fb7a7f6c120195c5a57faf78a321dbf65 (patch) | |
tree | 272eab3583e67cab24e9b9f92cc2e847368cb54b /Documentation | |
parent | 2fd4c50dbff19eb3d798236074bfa3226b5df4a6 (diff) | |
download | linux-0e242e3fb7a7f6c120195c5a57faf78a321dbf65.tar.bz2 |
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@kernel.org>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/networking/netdev-FAQ.rst | 3 |
1 files changed, 3 insertions, 0 deletions
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. |