From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Borislav Petkov <bp@alien8.de>, Hannu Hartikainen <hannu@hrtk.in>,
Jakub Kicinski <kuba@kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Lee Jones <lee.jones@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Thorsten Leemhuis <linux@leemhuis.info>,
linux-kernel@vger.kernel.org
Subject: [PATCH 4/4] Documentation/process: fix a cross reference
Date: Tue, 16 Nov 2021 12:11:23 +0000 [thread overview]
Message-ID: <f03c43389f024751e1056c54e240bef64ac4b2ed.1637064577.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1637064577.git.mchehab+huawei@kernel.org>
The cross-reference for the handbooks section works. However, it is
meant to describe the path inside the Kernel's doc where the section
is, but there's an space instead of a dash, plus it lacks the .rst at
the end, which makes:
./scripts/documentation-file-ref-check
to complain.
Fixes: 604370e106cc ("Documentation/process: Add maintainer handbooks section")
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
To mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH 0/4] at: https://lore.kernel.org/all/cover.1637064577.git.mchehab+huawei@kernel.org/
Documentation/process/submitting-patches.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
index a0cc96923ea7..da085d63af9b 100644
--- a/Documentation/process/submitting-patches.rst
+++ b/Documentation/process/submitting-patches.rst
@@ -22,8 +22,8 @@ use it, it will make your life as a kernel developer and in general much
easier.
Some subsystems and maintainer trees have additional information about
-their workflow and expectations, see :ref:`Documentation/process/maintainer
-handbooks <maintainer_handbooks_main>`.
+their workflow and expectations, see
+:ref:`Documentation/process/maintainer-handbooks.rst <maintainer_handbooks_main>`.
Obtain a current source tree
----------------------------
--
2.33.1
next prev parent reply other threads:[~2021-11-16 12:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 12:11 [PATCH 0/4] Address some bad references to Kernel docs Mauro Carvalho Chehab
2021-11-16 12:11 ` [PATCH 1/4] libbpf: update index.rst reference Mauro Carvalho Chehab
2021-11-16 12:11 ` [PATCH 2/4] docs: accounting: update delay-accounting.rst reference Mauro Carvalho Chehab
2021-11-16 12:11 ` [PATCH 3/4] Documentation: update vcpu-requests.rst reference Mauro Carvalho Chehab
2021-11-16 12:54 ` Paolo Bonzini
2021-11-16 14:01 ` Anup Patel
2021-11-16 18:05 ` Paolo Bonzini
2021-11-17 5:19 ` Anup Patel
2021-11-16 12:11 ` Mauro Carvalho Chehab [this message]
2021-11-17 13:12 ` [PATCH 0/4] Address some bad references to Kernel docs Jonathan Corbet
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=f03c43389f024751e1056c54e240bef64ac4b2ed.1637064577.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=hannu@hrtk.in \
--cc=konstantin@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®