linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Yanteng Si <siyanteng@loongson.cn>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.org>,
	linux-doc@vger.kernel.org
Subject: htmldocs: Warning: Documentation/translations/zh_CN/devicetree/changesets.rst references a file that doesn't exist: Documentation/Devicetree/changesets.rst
Date: Thu, 22 Sep 2022 14:38:14 +0800	[thread overview]
Message-ID: <202209221415.peH8XStP-lkp@intel.com> (raw)

tree:   git://git.lwn.net/linux.git docs-next
head:   a8249d62a611f398fafebbb8f6129888e98d5354
commit: 702f436ab07b88a778ced4561ad62dadb7c919c9 docs/zh_CN: add dt changesets translation
date:   10 hours ago
reproduce:
        git remote add lwn git://git.lwn.net/linux.git
        git fetch --no-tags lwn docs-next
        git checkout 702f436ab07b88a778ced4561ad62dadb7c919c9
        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>

All warnings (new ones prefixed by >>):

>> Warning: Documentation/translations/zh_CN/devicetree/changesets.rst references a file that doesn't exist: Documentation/Devicetree/changesets.rst

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

             reply	other threads:[~2022-09-22  6:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22  6:38 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-05  7:10 htmldocs: Warning: Documentation/translations/zh_CN/devicetree/changesets.rst references a file that doesn't exist: Documentation/Devicetree/changesets.rst kernel test robot

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=202209221415.peH8XStP-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=siyanteng@loongson.cn \
    /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).