From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
andrew@lunn.ch, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net v2 3/3] docs: netdev: add a cheat sheet for the rules
Date: Fri, 1 Jul 2022 20:12:09 -0700 [thread overview]
Message-ID: <20220702031209.790535-4-kuba@kernel.org> (raw)
In-Reply-To: <20220702031209.790535-1-kuba@kernel.org>
Summarize the rules we see broken most often and which may
be less familiar to kernel devs who are used to working outside
of netdev.
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
Documentation/process/maintainer-netdev.rst | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/Documentation/process/maintainer-netdev.rst b/Documentation/process/maintainer-netdev.rst
index 8a9dae7a0524..d14007081595 100644
--- a/Documentation/process/maintainer-netdev.rst
+++ b/Documentation/process/maintainer-netdev.rst
@@ -6,6 +6,15 @@
netdev FAQ
==========
+tl;dr
+-----
+
+ - designate your patch to a tree - ``[PATCH net]`` or ``[PATCH net-next]``
+ - for fixes the ``Fixes:`` tag is required, regardless of the tree
+ - don't post large series (> 15 patches), break them up
+ - don't repost your patches within one 24h period
+ - reverse xmas tree
+
What is netdev?
---------------
It is a mailing list for all network-related Linux stuff. This
--
2.36.1
next prev parent reply other threads:[~2022-07-02 3:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 3:12 [PATCH net v2 0/3] docs: netdev: document more of our rules Jakub Kicinski
2022-07-02 3:12 ` [PATCH net v2 1/3] docs: netdev: document that patch series length limit Jakub Kicinski
2022-07-02 20:14 ` Andrew Lunn
2022-07-02 3:12 ` [PATCH net v2 2/3] docs: netdev: document reverse xmas tree Jakub Kicinski
2022-07-02 20:15 ` Andrew Lunn
2022-07-02 3:12 ` Jakub Kicinski [this message]
2022-07-02 20:15 ` [PATCH net v2 3/3] docs: netdev: add a cheat sheet for the rules Andrew Lunn
2022-07-04 9:10 ` [PATCH net v2 0/3] docs: netdev: document more of our rules patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220702031209.790535-4-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.