netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net,
	bpf@vger.kernel.org, linux-doc@vger.kernel.org, andrew@lunn.ch,
	f.fainelli@gmail.com, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net v2 14/14] docs: netdev: move the netdev-FAQ to the process pages
Date: Mon, 28 Mar 2022 22:08:30 -0700	[thread overview]
Message-ID: <20220329050830.2755213-15-kuba@kernel.org> (raw)
In-Reply-To: <20220329050830.2755213-1-kuba@kernel.org>

The documentation for the tip tree is really in quite a similar
spirit to the netdev-FAQ. Move the netdev-FAQ to the process docs
as well.

Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
 Documentation/bpf/bpf_devel_QA.rst                             | 2 +-
 Documentation/networking/index.rst                             | 3 ++-
 Documentation/process/maintainer-handbooks.rst                 | 1 +
 .../netdev-FAQ.rst => process/maintainer-netdev.rst}           | 0
 MAINTAINERS                                                    | 1 +
 5 files changed, 5 insertions(+), 2 deletions(-)
 rename Documentation/{networking/netdev-FAQ.rst => process/maintainer-netdev.rst} (100%)

diff --git a/Documentation/bpf/bpf_devel_QA.rst b/Documentation/bpf/bpf_devel_QA.rst
index 253496af8fef..761474bd7fe6 100644
--- a/Documentation/bpf/bpf_devel_QA.rst
+++ b/Documentation/bpf/bpf_devel_QA.rst
@@ -658,7 +658,7 @@ Otherwise, you can use ``bpf`` target. Additionally, you *must* use bpf target
 
 .. Links
 .. _Documentation/process/: https://www.kernel.org/doc/html/latest/process/
-.. _netdev-FAQ: ../networking/netdev-FAQ.rst
+.. _netdev-FAQ: Documentation/process/maintainer-netdev.rst
 .. _selftests:
    https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/testing/selftests/bpf/
 .. _Documentation/dev-tools/kselftest.rst:
diff --git a/Documentation/networking/index.rst b/Documentation/networking/index.rst
index ce017136ab05..72cf33579b78 100644
--- a/Documentation/networking/index.rst
+++ b/Documentation/networking/index.rst
@@ -1,12 +1,13 @@
 Linux Networking Documentation
 ==============================
 
+Refer to :ref:`netdev-FAQ` for a guide on netdev development process specifics.
+
 Contents:
 
 .. toctree::
    :maxdepth: 2
 
-   netdev-FAQ
    af_xdp
    bareudp
    batman-adv
diff --git a/Documentation/process/maintainer-handbooks.rst b/Documentation/process/maintainer-handbooks.rst
index 6af1abb0da48..d783060b4cc6 100644
--- a/Documentation/process/maintainer-handbooks.rst
+++ b/Documentation/process/maintainer-handbooks.rst
@@ -16,3 +16,4 @@ which is supplementary to the general development process handbook
    :maxdepth: 2
 
    maintainer-tip
+   maintainer-netdev
diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/process/maintainer-netdev.rst
similarity index 100%
rename from Documentation/networking/netdev-FAQ.rst
rename to Documentation/process/maintainer-netdev.rst
diff --git a/MAINTAINERS b/MAINTAINERS
index 91c04cb65247..fc1ee838d103 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -13499,6 +13499,7 @@ B:	mailto:netdev@vger.kernel.org
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git
 F:	Documentation/networking/
+F:	Documentation/process/maintainer-netdev.rst
 F:	include/linux/in.h
 F:	include/linux/net.h
 F:	include/linux/netdevice.h
-- 
2.34.1


  parent reply	other threads:[~2022-03-29  5:09 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29  5:08 [PATCH net v2 00/14] docs: update and move the netdev-FAQ Jakub Kicinski
2022-03-29  5:08 ` [PATCH net v2 01/14] docs: netdev: replace references to old archives Jakub Kicinski
2022-03-30  3:30   ` Florian Fainelli
2022-03-29  5:08 ` [PATCH net v2 02/14] docs: netdev: minor reword Jakub Kicinski
2022-03-30  3:30   ` Florian Fainelli
2022-03-29  5:08 ` [PATCH net v2 03/14] docs: netdev: move the patch marking section up Jakub Kicinski
2022-03-29 12:52   ` Andrew Lunn
2022-03-30  3:30   ` Florian Fainelli
2022-03-29  5:08 ` [PATCH net v2 04/14] docs: netdev: turn the net-next closed into a Warning Jakub Kicinski
2022-03-30  3:30   ` Florian Fainelli
2022-03-29  5:08 ` [PATCH net v2 05/14] docs: netdev: note that RFC postings are allowed any time Jakub Kicinski
2022-03-29 12:53   ` Andrew Lunn
2022-03-30  3:31   ` Florian Fainelli
2022-03-29  5:08 ` [PATCH net v2 06/14] docs: netdev: shorten the name and mention msgid for patch status Jakub Kicinski
2022-03-30  3:31   ` Florian Fainelli
2022-03-29  5:08 ` [PATCH net v2 07/14] docs: netdev: rephrase the 'Under review' question Jakub Kicinski
2022-03-30  3:33   ` Florian Fainelli
2022-03-30  4:17     ` Jakub Kicinski
2022-03-29  5:08 ` [PATCH net v2 08/14] docs: netdev: rephrase the 'should I update patchwork' question Jakub Kicinski
2022-03-29  5:08 ` [PATCH net v2 09/14] docs: netdev: add a question about re-posting frequency Jakub Kicinski
2022-03-30  3:33   ` Florian Fainelli
2022-03-29  5:08 ` [PATCH net v2 10/14] docs: netdev: make the testing requirement more stringent Jakub Kicinski
2022-03-30  3:34   ` Florian Fainelli
2022-03-29  5:08 ` [PATCH net v2 11/14] docs: netdev: add missing back ticks Jakub Kicinski
2022-03-30  3:34   ` Florian Fainelli
2022-03-29  5:08 ` [PATCH net v2 12/14] docs: netdev: call out the merge window in tag checking Jakub Kicinski
2022-03-30  3:34   ` Florian Fainelli
2022-03-29  5:08 ` [PATCH net v2 13/14] docs: netdev: broaden the new vs old code formatting guidelines Jakub Kicinski
2022-03-30  3:34   ` Florian Fainelli
2022-03-29  5:08 ` Jakub Kicinski [this message]
2022-03-30  3:35   ` [PATCH net v2 14/14] docs: netdev: move the netdev-FAQ to the process pages Florian Fainelli

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=20220329050830.2755213-15-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=bpf@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).