From: kernel test robot <lkp@intel.com>
To: Dave Marchevsky <davemarchevsky@fb.com>
Cc: oe-kbuild-all@lists.linux.dev,
Ammar Faizi <ammarfaizi2@gnuweeb.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
Alexei Starovoitov <ast@kernel.org>,
linux-doc@vger.kernel.org
Subject: [ammarfaizi2-block:bpf/bpf-next/master 9/13] htmldocs: Documentation/bpf/graph_ds_impl.rst:62: WARNING: Error in "code-block" directive:
Date: Wed, 15 Feb 2023 11:56:54 +0800 [thread overview]
Message-ID: <202302151123.wUE5FYFx-lkp@intel.com> (raw)
tree: https://github.com/ammarfaizi2/linux-block bpf/bpf-next/master
head: 1f5dfcc78ab4cc06ce7dac9de6c1ed361fde7119
commit: c31315c3aa09297d99cb39e837185ef225586d2b [9/13] bpf, documentation: Add graph documentation for non-owning refs
reproduce:
# https://github.com/ammarfaizi2/linux-block/commit/c31315c3aa09297d99cb39e837185ef225586d2b
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block bpf/bpf-next/master
git checkout c31315c3aa09297d99cb39e837185ef225586d2b
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>
| Link: https://lore.kernel.org/oe-kbuild-all/202302151123.wUE5FYFx-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/bpf/graph_ds_impl.rst:62: WARNING: Error in "code-block" directive:
vim +62 Documentation/bpf/graph_ds_impl.rst
61
> 62 .. code-block:: c
63 struct node_data {
64 long key;
65 long data;
66 struct bpf_rb_node node;
67 };
68
69 struct bpf_spin_lock glock;
70 struct bpf_rb_root groot __contains(node_data, node);
71
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-02-15 3:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202302151123.wUE5FYFx-lkp@intel.com \
--to=lkp@intel.com \
--cc=ammarfaizi2@gnuweeb.org \
--cc=ast@kernel.org \
--cc=davemarchevsky@fb.com \
--cc=gwml@vger.gnuweeb.org \
--cc=linux-doc@vger.kernel.org \
--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 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.