redonkable
/
alistair23-linux
1
0
Fork 0
Code Releases Activity

docs: Update references to netdev-FAQ 

File 'Documentation/networking/netdev-FAQ.txt' has been converted to RST
format.  We should update all links/references to point to the new file.

Update references to netdev-FAQ

Signed-off-by: Tobin C. Harding <me@tobin.cc>
Signed-off-by: David S. Miller <davem@davemloft.net>
hifive-unleashed-5.1
Tobin C. Harding 2018-07-26 15:02:26 +10:00 committed by David S. Miller
parent 96398ddf63
commit 287f4fa99a
2 changed files with 10 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
Documentation/bpf/bpf_devel_QA.rst
View File

@ -106,9 +106,9 @@ into the bpf-next tree will make their way into net-next tree. net and
net-next are both run by David S. Miller. From there, they will go net-next are both run by David S. Miller. From there, they will go
into the kernel mainline tree run by Linus Torvalds. To read up on the into the kernel mainline tree run by Linus Torvalds. To read up on the
process of net and net-next being merged into the mainline tree, see process of net and net-next being merged into the mainline tree, see
the `netdev FAQ`_ under: the :ref:`netdev-FAQ`
`Documentation/networking/netdev-FAQ.txt`_
Occasionally, to prevent merge conflicts, we might send pull requests Occasionally, to prevent merge conflicts, we might send pull requests
to other trees (e.g. tracing) with a small subset of the patches, but to other trees (e.g. tracing) with a small subset of the patches, but
@ -125,8 +125,8 @@ request)::
Q: How do I indicate which tree (bpf vs. bpf-next) my patch should be applied to? Q: How do I indicate which tree (bpf vs. bpf-next) my patch should be applied to?
--------------------------------------------------------------------------------- ---------------------------------------------------------------------------------
A: The process is the very same as described in the `netdev FAQ`_, so A: The process is the very same as described in the :ref:`netdev-FAQ`,
please read up on it. The subject line must indicate whether the so please read up on it. The subject line must indicate whether the
patch is a fix or rather "next-like" content in order to let the patch is a fix or rather "next-like" content in order to let the
maintainers know whether it is targeted at bpf or bpf-next. maintainers know whether it is targeted at bpf or bpf-next.
@ -184,7 +184,7 @@ ii) run extensive BPF test suite and
Once the BPF pull request was accepted by David S. Miller, then Once the BPF pull request was accepted by David S. Miller, then
the patches end up in net or net-next tree, respectively, and the patches end up in net or net-next tree, respectively, and
make their way from there further into mainline. Again, see the make their way from there further into mainline. Again, see the
`netdev FAQ`_ for additional information e.g. on how often they are :ref:`netdev-FAQ` for additional information e.g. on how often they are
merged to mainline. merged to mainline.
Q: How long do I need to wait for feedback on my BPF patches? Q: How long do I need to wait for feedback on my BPF patches?
@ -208,7 +208,7 @@ Q: Are patches applied to bpf-next when the merge window is open?
----------------------------------------------------------------- -----------------------------------------------------------------
A: For the time when the merge window is open, bpf-next will not be A: For the time when the merge window is open, bpf-next will not be
processed. This is roughly analogous to net-next patch processing, processed. This is roughly analogous to net-next patch processing,
so feel free to read up on the `netdev FAQ`_ about further details. so feel free to read up on the :ref:`netdev-FAQ` about further details.
During those two weeks of merge window, we might ask you to resend During those two weeks of merge window, we might ask you to resend
your patch series once bpf-next is open again. Once Linus released your patch series once bpf-next is open again. Once Linus released
@ -372,7 +372,7 @@ netdev kernel mailing list in Cc and ask for the fix to be queued up:
netdev@vger.kernel.org netdev@vger.kernel.org
The process in general is the same as on netdev itself, see also the The process in general is the same as on netdev itself, see also the
`netdev FAQ`_ document. :ref:`netdev-FAQ`.
Q: Do you also backport to kernels not currently maintained as stable? Q: Do you also backport to kernels not currently maintained as stable?
---------------------------------------------------------------------- ----------------------------------------------------------------------
@ -388,9 +388,7 @@ Q: The BPF patch I am about to submit needs to go to stable as well
What should I do? What should I do?
A: The same rules apply as with netdev patch submissions in general, see A: The same rules apply as with netdev patch submissions in general, see
`netdev FAQ`_ under: the :ref:`netdev-FAQ`.
`Documentation/networking/netdev-FAQ.txt`_
Never add "``Cc: stable@vger.kernel.org``" to the patch description, but Never add "``Cc: stable@vger.kernel.org``" to the patch description, but
ask the BPF maintainers to queue the patches instead. This can be done ask the BPF maintainers to queue the patches instead. This can be done
@ -630,8 +628,7 @@ when:
.. Links .. Links
.. _Documentation/process/: https://www.kernel.org/doc/html/latest/process/ .. _Documentation/process/: https://www.kernel.org/doc/html/latest/process/
.. _MAINTAINERS: ../../MAINTAINERS .. _MAINTAINERS: ../../MAINTAINERS
.. _Documentation/networking/netdev-FAQ.txt: ../networking/netdev-FAQ.txt .. _netdev-FAQ: ../networking/netdev-FAQ.rst
.. _netdev FAQ: ../networking/netdev-FAQ.txt
.. _samples/bpf/: ../../samples/bpf/ .. _samples/bpf/: ../../samples/bpf/
.. _selftests: ../../tools/testing/selftests/bpf/ .. _selftests: ../../tools/testing/selftests/bpf/
.. _Documentation/dev-tools/kselftest.rst: .. _Documentation/dev-tools/kselftest.rst:

2
Documentation/process/stable-kernel-rules.rst
View File

@ -37,7 +37,7 @@ Procedure for submitting patches to the -stable tree
- If the patch covers files in net/ or drivers/net please follow netdev stable - If the patch covers files in net/ or drivers/net please follow netdev stable
submission guidelines as described in submission guidelines as described in
Documentation/networking/netdev-FAQ.txt :ref:`Documentation/networking/netdev-FAQ.rst <netdev-FAQ>`
- Security patches should not be handled (solely) by the -stable review - Security patches should not be handled (solely) by the -stable review
process but should follow the procedures in process but should follow the procedures in
:ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>`. :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>`.