From: Jonathan Corbet <corbet@lwn.net>
To: kernel test robot <lkp@intel.com>, Kees Cook <keescook@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-doc@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [lwn:docs-next 12/12] htmldocs: Warning: Documentation/process/2.Process.rst references a file that doesn't exist: Documentation/process/submittingpatches.rst
Date: Sat, 20 May 2023 08:10:20 -0600 [thread overview]
Message-ID: <87v8gnjdpv.fsf@meer.lwn.net> (raw)
In-Reply-To: <202305201652.POM84URe-lkp@intel.com>
kernel test robot <lkp@intel.com> writes:
> tree: git://git.lwn.net/linux.git docs-next
> head: 329ac9af902e441bae13803a4d7126aaf5984188
> commit: 329ac9af902e441bae13803a4d7126aaf5984188 [12/12] docs: submitting-patches: Discuss interleaved replies
> reproduce:
> git remote add lwn git://git.lwn.net/linux.git
> git fetch --no-tags lwn docs-next
> git checkout 329ac9af902e441bae13803a4d7126aaf5984188
> make menuconfig
> # enable CONFIG_COMPILE_TEST, CONFIG_WARN_MISSING_DOCUMENTS, CONFIG_WARN_ABI_ERRORS
> make htmldocs
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202305201652.POM84URe-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
>>> Warning: Documentation/process/2.Process.rst references a file that doesn't exist: Documentation/process/submittingpatches.rst
Oops...I need to figure out why I didn't notice that. I've dropped the
following in to make this go away.
Thanks,
jon
From a1d2c9b3029de24505c09430931966b96fe1b678 Mon Sep 17 00:00:00 2001
From: Jonathan Corbet <corbet@lwn.net>
Date: Sat, 20 May 2023 08:07:04 -0600
Subject: [PATCH] docs: process: fix a typoed cross-reference
Commit 329ac9af902e added a cross-reference missing a hyphen; add one from
my emergency hyphen stash.
Reported-by: kernel test robot <lkp@intel.com>
Fixes: 329ac9af902e ("docs: submitting-patches: Discuss interleaved replies")
Closes: https://lore.kernel.org/oe-kbuild-all/202305201652.POM84URe-lkp@intel.com/
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
---
Documentation/process/2.Process.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/process/2.Process.rst b/Documentation/process/2.Process.rst
index 9ab58a0d4fac..613a01da4717 100644
--- a/Documentation/process/2.Process.rst
+++ b/Documentation/process/2.Process.rst
@@ -437,7 +437,7 @@ There are a few hints which can help with linux-kernel survival:
- Use interleaved ("inline") replies, which makes your response easier to
read. (i.e. avoid top-posting -- the practice of putting your answer above
the quoted text you are responding to.) For more details, see
- :ref:`Documentation/process/submittingpatches.rst <interleaved_replies>`.
+ :ref:`Documentation/process/submitting-patches.rst <interleaved_replies>`.
- Ask on the correct mailing list. Linux-kernel may be the general meeting
point, but it is not the best place to find developers from all
--
2.40.1
prev parent reply other threads:[~2023-05-20 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-20 8:30 [lwn:docs-next 12/12] htmldocs: Warning: Documentation/process/2.Process.rst references a file that doesn't exist: Documentation/process/submittingpatches.rst kernel test robot
2023-05-20 14:10 ` Jonathan Corbet [this message]
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=87v8gnjdpv.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=keescook@chromium.org \
--cc=krzk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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).