kernel test robot <lkp@xxxxxxxxx> 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@xxxxxxxxx> > | Closes: https://lore.kernel.org/oe-kbuild-all/202305201652.POM84URe-lkp@xxxxxxxxx/ > > 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@xxxxxxx> 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@xxxxxxxxx> Fixes: 329ac9af902e ("docs: submitting-patches: Discuss interleaved replies") Closes: https://lore.kernel.org/oe-kbuild-all/202305201652.POM84URe-lkp@xxxxxxxxx/ Signed-off-by: Jonathan Corbet <corbet@xxxxxxx> --- 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
