From: kernel test robot <lkp@intel.com>
To: Dave Thaler <dthaler1968@googlemail.com>, bpf@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, bpf@ietf.org,
Dave Thaler <dthaler@microsoft.com>
Subject: Re: [PATCH bpf-next v2] bpf, docs: Explain helper functions
Date: Mon, 13 Feb 2023 07:20:03 +0800 [thread overview]
Message-ID: <202302130706.NBSii5FS-lkp@intel.com> (raw)
In-Reply-To: <20230206191647.2075-1-dthaler1968@googlemail.com>
Hi Dave,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Dave-Thaler/bpf-docs-Explain-helper-functions/20230207-031845
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link: https://lore.kernel.org/r/20230206191647.2075-1-dthaler1968%40googlemail.com
patch subject: [PATCH bpf-next v2] bpf, docs: Explain helper functions
reproduce:
# https://github.com/intel-lab-lkp/linux/commit/b579d93fed53b16ad7241911226cbeb3b42f8266
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Dave-Thaler/bpf-docs-Explain-helper-functions/20230207-031845
git checkout b579d93fed53b16ad7241911226cbeb3b42f8266
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/202302130706.NBSii5FS-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/bpf/clang-notes.rst:24: WARNING: Title underline too short.
vim +24 Documentation/bpf/clang-notes.rst
22
23 Reserved instructions
> 24 ====================
25
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
prev parent reply other threads:[~2023-02-12 23:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 19:16 [PATCH bpf-next v2] bpf, docs: Explain helper functions Dave Thaler
2023-02-08 15:10 ` [Bpf] " David Vernet
2023-02-08 17:26 ` Dave Thaler
2023-02-08 17:29 ` David Vernet
2023-02-08 17:31 ` Alexei Starovoitov
2023-02-08 17:40 ` David Vernet
2023-02-08 17:45 ` Dave Thaler
2023-02-09 16:04 ` David Vernet
2023-02-12 23:20 ` kernel test robot [this message]
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=202302130706.NBSii5FS-lkp@intel.com \
--to=lkp@intel.com \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=dthaler1968@googlemail.com \
--cc=dthaler@microsoft.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