public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>,
	kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-doc@vger.kernel.org
Subject: Re: [bpf:master 6/15] htmldocs: Warning: Documentation/bpf/btf.rst references a file that doesn't exist: Documentation/bpf/llvm_reloc
Date: Fri, 01 Sep 2023 14:18:45 +0300	[thread overview]
Message-ID: <5009129a873cf20adacd679d5073c799f79672d2.camel@gmail.com> (raw)
In-Reply-To: <a62b47218f1852d09b243b8fb1741c2baca4d336.camel@gmail.com>

On Fri, 2023-09-01 at 12:26 +0300, Eduard Zingerman wrote:
> On Fri, 2023-09-01 at 08:29 +0200, Daniel Borkmann wrote:
> > Hi Eduard,
> > 
> > On 9/1/23 2:05 AM, kernel test robot wrote:
> > > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git master
> > > head:   be8e754cbfac698d6304bb8382c8d18ac74424d3
> > > commit: be4033d36070e44fba766a21ef2d0c24fa04c377 [6/15] docs/bpf: Add description for CO-RE relocations
> > > reproduce: (https://download.01.org/0day-ci/archive/20230901/202309010804.G3MpXo59-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/202309010804.G3MpXo59-lkp@intel.com/
> > > 
> > > All warnings (new ones prefixed by >>):
> > > 
> > > > > Warning: Documentation/bpf/btf.rst references a file that doesn't exist: Documentation/bpf/llvm_reloc
> > > > > Warning: Documentation/bpf/llvm_reloc.rst references a file that doesn't exist: Documentation/bpf/btf
> > 
> > Could you send a follow-up fix for bpf tree?
> 
> Hi Daniel,
> 
> Will send the fix shortly. Strangely, I did check this syntax locally
> before sending the original patch, and had no warnings reported.

I followed reproducing instructions but can't trigger this warning,
tried several sphinx versions:
- 1.7.9
- 2.4.4
- 4.3.2

I'll remove 'Documentation/bpf/llvm_reloc' and 'Documentation/bpf/btf'
labels from the documents (and these are link labels, not actual
links), but it looks like I don't have a way to check the results in a
way compatible with test robot.

  reply	other threads:[~2023-09-01 11:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01  0:05 [bpf:master 6/15] htmldocs: Warning: Documentation/bpf/btf.rst references a file that doesn't exist: Documentation/bpf/llvm_reloc kernel test robot
2023-09-01  6:29 ` Daniel Borkmann
2023-09-01  9:26   ` Eduard Zingerman
2023-09-01 11:18     ` Eduard Zingerman [this message]
2023-09-01 11:22       ` Daniel Borkmann
2023-09-01 11:48         ` Eduard Zingerman
2023-09-01 12:23           ` Philip Li
2023-09-01 12:27             ` Eduard Zingerman
2023-09-01 12:33               ` Philip Li
2023-09-01 12:49                 ` Daniel Borkmann
2023-09-01 12:57                   ` Philip Li
2023-09-11 13:44                     ` 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=5009129a873cf20adacd679d5073c799f79672d2.camel@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=linux-doc@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