mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Federico Vaga <federico.vaga@vaga.pv.it>
To: kernel test robot <lkp@intel.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	oe-kbuild-all@lists.linux.dev, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] doc:it_IT: update documents in process/
Date: Fri, 27 Sep 2024 11:55:20 +0200	[thread overview]
Message-ID: <d50ee871d2bdc35192be9729176759a1@vaga.pv.it> (raw)
In-Reply-To: <202409250825.r3iY80XD-lkp@intel.com>

I'll come back with a fix for this warning.

On 2024-09-25 02:41, kernel test robot wrote:
> Hi Federico,
> 
> kernel test robot noticed the following build warnings:
> 
> [auto build test WARNING on lwn/docs-next]
> [also build test WARNING on next-20240924]
> [cannot apply to linus/master v6.11]
> [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/Federico-Vaga/doc-it_IT-update-documents-in-process/20240925-064806
> base:   git://git.lwn.net/linux.git docs-next
> patch link:
> https://lore.kernel.org/r/20240924224635.21472-1-federico.vaga%40vaga.pv.it
> patch subject: [PATCH v2] doc:it_IT: update documents in process/
> reproduce:
> (https://download.01.org/0day-ci/archive/20240925/202409250825.r3iY80XD-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new 
> version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes:
> https://lore.kernel.org/oe-kbuild-all/202409250825.r3iY80XD-lkp@intel.com/
> 
> All warnings (new ones prefixed by >>):
> 
>    Documentation/userspace-api/netlink/netlink-raw.rst:
> :doc:`tc<../../networking/netlink_spec/tc>`
>    Documentation/userspace-api/netlink/netlink-raw.rst:
> :doc:`tc<../../networking/netlink_spec/tc>`
>    Warning: Documentation/devicetree/bindings/power/wakeup-source.txt
> references a file that doesn't exist:
> Documentation/devicetree/bindings/input/qcom,pm8xxx-keypad.txt
>    Warning:
> Documentation/devicetree/bindings/regulator/siliconmitus,sm5703-regulator.yaml
> references a file that doesn't exist:
> Documentation/devicetree/bindings/mfd/siliconmitus,sm5703.yaml
>    Warning: Documentation/hwmon/g762.rst references a file that
> doesn't exist: Documentation/devicetree/bindings/hwmon/g762.txt
>>> Warning: Documentation/translations/it_IT/process/4.Coding.rst 
>>> references a file that doesn't exist: 
>>> Documentation/translations/it_IT/process/clang-format.rst
>>> Warning: Documentation/translations/it_IT/process/coding-style.rst 
>>> references a file that doesn't exist: 
>>> Documentation/translations/it_IT/process/clang-format.rst
>    Warning: Documentation/userspace-api/netlink/index.rst references a
> file that doesn't exist:
> Documentation/networking/netlink_spec/index.rst
>    Warning: Documentation/userspace-api/netlink/specs.rst references a
> file that doesn't exist:
> Documentation/networking/netlink_spec/index.rst
>    Warning: MAINTAINERS references a file that doesn't exist:
> Documentation/devicetree/bindings/reserved-memory/qcom
>    Warning: MAINTAINERS references a file that doesn't exist:
> Documentation/devicetree/bindings/display/exynos/
>    Warning: MAINTAINERS references a file that doesn't exist:
> Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt

-- 
Federico Vaga
http://www.federicovaga.it/

      reply	other threads:[~2024-09-27  9:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24 22:46 Federico Vaga
2024-09-25  0:41 ` kernel test robot
2024-09-27  9:55   ` Federico Vaga [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=d50ee871d2bdc35192be9729176759a1@vaga.pv.it \
    --to=federico.vaga@vaga.pv.it \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®