From: Jonathan Corbet <corbet@lwn.net>
To: kernel test robot <lkp@intel.com>, linux-doc@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Chen-Yu Tsai" <wens@csie.org>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Samuel Holland" <samuel@sholland.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-input@vger.kernel.org, linux-sunxi@lists.linux.dev,
linux-pwm@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH 6/7] docs: update some straggling Documentation/arm references
Date: Sat, 20 May 2023 08:12:47 -0600 [thread overview]
Message-ID: <87r0rbjdls.fsf@meer.lwn.net> (raw)
In-Reply-To: <202305201023.2DYXmdv3-lkp@intel.com>
kernel test robot <lkp@intel.com> writes:
> Hi Jonathan,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on linus/master]
> [also build test WARNING on v6.4-rc2 next-20230519]
> [cannot apply to sunxi/sunxi/for-next arm64/for-next/core thierry-reding-pwm/for-next]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Jonathan-Corbet/arm-docs-Move-Arm-documentation-to-Documentation-arch/20230520-005124
> base: linus/master
> patch link: https://lore.kernel.org/r/20230519164607.38845-7-corbet%40lwn.net
> patch subject: [PATCH 6/7] docs: update some straggling Documentation/arm references
> reproduce:
> # https://github.com/intel-lab-lkp/linux/commit/3c9885f2702a3319156cfbacedfca658e726213b
> git remote add linux-review https://github.com/intel-lab-lkp/linux
> git fetch --no-tags linux-review Jonathan-Corbet/arm-docs-Move-Arm-documentation-to-Documentation-arch/20230520-005124
> git checkout 3c9885f2702a3319156cfbacedfca658e726213b
> 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/202305201023.2DYXmdv3-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
>>> Warning: MAINTAINERS references a file that doesn't exist: Documentation/arch/arm64/
Sigh...obviously this hunk:
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
S: Maintained
T: git git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
-F: Documentation/arm64/
+F: Documentation/arch/arm64/
F: arch/arm64/
F: tools/testing/selftests/arm64/
...got a bit ahead of the game. I'll take that one out, sorry for the
noise.
jon
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: kernel test robot <lkp@intel.com>, linux-doc@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Chen-Yu Tsai" <wens@csie.org>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Samuel Holland" <samuel@sholland.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-input@vger.kernel.org, linux-sunxi@lists.linux.dev,
linux-pwm@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH 6/7] docs: update some straggling Documentation/arm references
Date: Sat, 20 May 2023 08:12:47 -0600 [thread overview]
Message-ID: <87r0rbjdls.fsf@meer.lwn.net> (raw)
In-Reply-To: <202305201023.2DYXmdv3-lkp@intel.com>
kernel test robot <lkp@intel.com> writes:
> Hi Jonathan,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on linus/master]
> [also build test WARNING on v6.4-rc2 next-20230519]
> [cannot apply to sunxi/sunxi/for-next arm64/for-next/core thierry-reding-pwm/for-next]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Jonathan-Corbet/arm-docs-Move-Arm-documentation-to-Documentation-arch/20230520-005124
> base: linus/master
> patch link: https://lore.kernel.org/r/20230519164607.38845-7-corbet%40lwn.net
> patch subject: [PATCH 6/7] docs: update some straggling Documentation/arm references
> reproduce:
> # https://github.com/intel-lab-lkp/linux/commit/3c9885f2702a3319156cfbacedfca658e726213b
> git remote add linux-review https://github.com/intel-lab-lkp/linux
> git fetch --no-tags linux-review Jonathan-Corbet/arm-docs-Move-Arm-documentation-to-Documentation-arch/20230520-005124
> git checkout 3c9885f2702a3319156cfbacedfca658e726213b
> 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/202305201023.2DYXmdv3-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
>>> Warning: MAINTAINERS references a file that doesn't exist: Documentation/arch/arm64/
Sigh...obviously this hunk:
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
S: Maintained
T: git git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
-F: Documentation/arm64/
+F: Documentation/arch/arm64/
F: arch/arm64/
F: tools/testing/selftests/arm64/
...got a bit ahead of the game. I'll take that one out, sorry for the
noise.
jon
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-05-20 14:12 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 16:46 [PATCH 0/7] docs: Move Documentation/arm under Documentation/arch Jonathan Corbet
2023-05-19 16:46 ` Jonathan Corbet
2023-05-19 16:46 ` [PATCH 1/7] arm: docs: Move Arm documentation to Documentation/arch/ Jonathan Corbet
2023-05-19 16:46 ` Jonathan Corbet
2023-05-20 1:41 ` Yanteng Si
2023-05-22 7:46 ` Alexandre TORGUE
2023-05-22 7:46 ` Alexandre TORGUE
2023-05-23 11:44 ` Robin Murphy
2023-05-23 11:44 ` Robin Murphy
2023-05-19 16:46 ` [PATCH 2/7] arm: update in-source documentation references Jonathan Corbet
2023-05-19 16:46 ` Jonathan Corbet
2023-05-19 16:46 ` [PATCH 3/7] arm64: Update Documentation/arm references Jonathan Corbet
2023-05-19 16:46 ` Jonathan Corbet
2023-05-23 9:42 ` Catalin Marinas
2023-05-23 9:42 ` Catalin Marinas
2023-05-19 16:46 ` [PATCH 4/7] mips: update a reference to a moved Arm Document Jonathan Corbet
2023-05-19 16:46 ` Jonathan Corbet
2023-05-19 21:25 ` Florian Fainelli
2023-05-19 21:25 ` Florian Fainelli
2023-06-12 23:40 ` Philippe Mathieu-Daudé
2023-06-12 23:40 ` Philippe Mathieu-Daudé
2023-05-19 16:46 ` [PATCH 5/7] crypto: update some Arm documentation references Jonathan Corbet
2023-05-19 16:46 ` Jonathan Corbet
2023-05-19 16:46 ` [PATCH 6/7] docs: update some straggling Documentation/arm references Jonathan Corbet
2023-05-19 16:46 ` Jonathan Corbet
2023-05-20 3:09 ` kernel test robot
2023-05-20 3:09 ` kernel test robot
2023-05-20 14:12 ` Jonathan Corbet [this message]
2023-05-20 14:12 ` Jonathan Corbet
2023-05-19 16:46 ` [PATCH 7/7] dt-bindings: Update " Jonathan Corbet
2023-05-19 16:46 ` Jonathan Corbet
2023-05-19 16:54 ` Conor Dooley
2023-05-19 16:54 ` Conor Dooley
2023-05-19 17:05 ` Jonathan Corbet
2023-05-19 17:05 ` 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=87r0rbjdls.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=samuel@sholland.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wens@csie.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.