From: kernel test robot <lkp@intel.com>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>, bpf <bpf@vger.kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
bpf@ietf.org
Subject: Re: [PATCH] bpf, docs: Document BPF insn encoding in term of stored bytes
Date: Sat, 25 Feb 2023 21:07:20 +0800 [thread overview]
Message-ID: <202302252028.csJFgGqg-lkp@intel.com> (raw)
In-Reply-To: <87y1om25l4.fsf@oracle.com>
Hi Jose,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on bpf-next/master]
[cannot apply to bpf/master linus/master v6.2 next-20230225]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Jose-E-Marchesi/bpf-docs-Document-BPF-insn-encoding-in-term-of-stored-bytes/20230225-040647
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link: https://lore.kernel.org/r/87y1om25l4.fsf%40oracle.com
patch subject: [PATCH] bpf, docs: Document BPF insn encoding in term of stored bytes
reproduce:
# https://github.com/intel-lab-lkp/linux/commit/018d3423bad903b4544673361f6df2ea28ce047a
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Jose-E-Marchesi/bpf-docs-Document-BPF-insn-encoding-in-term-of-stored-bytes/20230225-040647
git checkout 018d3423bad903b4544673361f6df2ea28ce047a
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/202302252028.csJFgGqg-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/bpf/instruction-set.rst:75: WARNING: Definition list ends without a blank line; unexpected unindent.
vim +75 Documentation/bpf/instruction-set.rst
70
71 opcode offset imm assembly
72 src dst
73 07 0 1 00 00 44 33 22 11 r1 += 0x11223344 // little
74 dst src
> 75 07 1 0 00 00 11 22 33 44 r1 += 0x11223344 // big
76
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-02-25 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 20:04 [PATCH] bpf, docs: Document BPF insn encoding in term of stored bytes Jose E. Marchesi
2023-02-24 20:44 ` [Bpf] " Dave Thaler
2023-02-24 20:59 ` Jose E. Marchesi
2023-02-25 0:20 ` Alexei Starovoitov
2023-02-25 13:07 ` kernel test robot [this message]
2023-02-27 16:52 ` David Vernet
2023-02-27 18:05 ` Jose E. Marchesi
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=202302252028.csJFgGqg-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=jose.marchesi@oracle.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