linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: Dave Thaler <dthaler@microsoft.com>,
	kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Alexei Starovoitov <ast@kernel.org>,
	linux-doc@vger.kernel.org
Subject: Re: [bpf-next:master 7/11] htmldocs: Documentation/bpf/linux-notes.rst:55: WARNING: Malformed table.
Date: Sat, 1 Oct 2022 08:45:23 -0700	[thread overview]
Message-ID: <CAADnVQL9S5gwykdxQoGjOzuAewpLMX+sgZ0RVo7yD4e4vumb4w@mail.gmail.com> (raw)
In-Reply-To: <202210012320.xRNBamDx-lkp@intel.com>

Dave,

please take a look.
Thanks!

On Sat, Oct 1, 2022 at 8:28 AM kernel test robot <lkp@intel.com> wrote:
>
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
> head:   5f388bba7acbdb097a9e7ed932a39b40f7eb2acf
> commit: 6166da0a02cde26c065692d0c05eb685178fee75 [7/11] bpf, docs: Move legacy packet instructions to a separate file
> reproduce:
>         # https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=6166da0a02cde26c065692d0c05eb685178fee75
>         git remote add bpf-next https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
>         git fetch --no-tags bpf-next master
>         git checkout 6166da0a02cde26c065692d0c05eb685178fee75
>         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 >>):
>
> >> Documentation/bpf/linux-notes.rst:55: WARNING: Malformed table.
> >> Documentation/bpf/linux-notes.rst:58: WARNING: Blank line required after table.
> >> Documentation/bpf/linux-notes.rst: WARNING: document isn't included in any toctree
>
> vim +55 Documentation/bpf/linux-notes.rst
>
>     54
>   > 55  ======  ====  ===================================================  =============
>     56  opcode  imm   description                                          reference
>     57  ======  ====  ===================================================  =============
>   > 58  0x20    any   dst = ntohl(\*(uint32_t \*)(R6->data + imm))         `Legacy BPF Packet access instructions`_
>
> --
> 0-DAY CI Kernel Test Service
> https://01.org/lkp

  reply	other threads:[~2022-10-01 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-01 15:26 [bpf-next:master 7/11] htmldocs: Documentation/bpf/linux-notes.rst:55: WARNING: Malformed table kernel test robot
2022-10-01 15:45 ` Alexei Starovoitov [this message]
2022-10-01 15:52   ` Alexei Starovoitov

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=CAADnVQL9S5gwykdxQoGjOzuAewpLMX+sgZ0RVo7yD4e4vumb4w@mail.gmail.com \
    --to=alexei.starovoitov@gmail.com \
    --cc=ast@kernel.org \
    --cc=dthaler@microsoft.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    /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).