From: Philip Li <philip.li@intel.com>
To: Alex Shi <seakeel@gmail.com>
Cc: Yanteng Si <si.yanteng@linux.dev>,
kernel test robot <lkp@intel.com>,
<oe-kbuild-all@lists.linux.dev>, <linux-doc@vger.kernel.org>,
Alex Shi <alexs@kernel.org>, Dongliang Mu <dzm91@hust.edu.cn>
Subject: Re: [lwn:docs-next 37/72] htmldocs: Warning: Documentation/translations/zh_CN/how-to.rst references a file that doesn't exist: Documentation/xxx/xxx.rst
Date: Mon, 19 May 2025 11:11:03 +0800 [thread overview]
Message-ID: <aCqhRwOxvUiCFtpN@rli9-mobl> (raw)
In-Reply-To: <CAJy-AmmsqK3x97yncNrnugCNrf5qNOTUwixFNiBifqigLrp2zQ@mail.gmail.com>
On Mon, May 19, 2025 at 10:24:20AM +0800, Alex Shi wrote:
> Yanteng Si <si.yanteng@linux.dev> 于2025年5月16日周五 18:02写道：
> >
> > Hi robot,
> >
> > 在 5/16/25 7:04 AM, kernel test robot 写道:
> > > Warning: Documentation/translations/zh_CN/how-to.rst references a file that doesn't exist: Documentation/xxx/xxx.rst
> >
> > I didn't reproduce this warning locally. It seems to be a difference
> >
> > between different versions of Sphinx.
> >
> > Could you please provide your Sphinx version?
>
>
> I can't reproduce it too. My sphinx tools version is 7.2.6.
> And it looks like a incorrect warnning.
Sorry for late response, the Sphinx version the bot use is 2.4.4, and it also enables
kconfigs like CONFIG_COMPILE_TEST, CONFIG_WARN_MISSING_DOCUMENTS, CONFIG_WARN_ABI_ERRORS,
refer to [1] for detail. Hope this is useful.
[1] https://download.01.org/0day-ci/archive/20250516/202505160627.WtzIIpL6-lkp@intel.com/reproduce
>
> Alex
>
next prev parent reply other threads:[~2025-05-19 3:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 23:04 [lwn:docs-next 37/72] htmldocs: Warning: Documentation/translations/zh_CN/how-to.rst references a file that doesn't exist: Documentation/xxx/xxx.rst kernel test robot
2025-05-16 10:01 ` Yanteng Si
2025-05-19 2:24 ` Alex Shi
2025-05-19 3:11 ` Philip Li [this message]
2025-05-19 3:34 ` Randy Dunlap
2025-05-19 3:57 ` Dongliang Mu
2025-05-19 4:13 ` Philip Li
2025-05-19 4:12 ` Philip Li
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=aCqhRwOxvUiCFtpN@rli9-mobl \
--to=philip.li@intel.com \
--cc=alexs@kernel.org \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=seakeel@gmail.com \
--cc=si.yanteng@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 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.