From: kbuild test robot <lkp@intel.com>
To: Martin KaFai Lau <kafai@fb.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
Alexei Starovoitov <ast@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@fb.com
Subject: Re: [PATCH bpf-next 07/10] bpf: btf: Add pretty print support to the basic arraymap
Date: Sat, 31 Mar 2018 17:12:36 +0800 [thread overview]
Message-ID: <201803311609.tsZ62eCl%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180330182643.3539371-8-kafai@fb.com>
Hi Martin,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on bpf-next/master]
url: https://github.com/0day-ci/linux/commits/Martin-KaFai-Lau/BTF-BPF-Type-Format/20180331-144656
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> kernel/bpf/inode.c:195:6: sparse: symbol 'map_seq_next' was not declared. Should it be static?
>> kernel/bpf/inode.c:282:30: sparse: symbol 'bpffs_map_fops' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2018-03-31 9:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 18:26 [PATCH bpf-next 00/10] BTF: BPF Type Format Martin KaFai Lau
2018-03-30 18:26 ` [PATCH bpf-next 01/10] bpf: btf: Introduce BPF Type Format (BTF) Martin KaFai Lau
2018-03-30 23:22 ` Daniel Borkmann
2018-03-30 23:32 ` Martin KaFai Lau
2018-03-31 8:43 ` kbuild test robot
2018-03-31 15:45 ` Martin KaFai Lau
2018-03-31 8:43 ` [RFC PATCH] bpf: btf: enum_ops can be static kbuild test robot
2018-03-30 18:26 ` [PATCH bpf-next 02/10] bpf: btf: Validate type reference Martin KaFai Lau
2018-03-30 18:26 ` [PATCH bpf-next 03/10] bpf: btf: Check members of struct/union Martin KaFai Lau
2018-03-30 18:26 ` [PATCH bpf-next 04/10] bpf: btf: Add pretty print capability for data with BTF type info Martin KaFai Lau
2018-03-30 18:26 ` [PATCH bpf-next 05/10] bpf: btf: Add BPF_BTF_LOAD command Martin KaFai Lau
2018-03-30 18:26 ` [PATCH bpf-next 06/10] bpf: btf: Add BPF_OBJ_GET_INFO_BY_FD support to BTF fd Martin KaFai Lau
2018-03-30 18:26 ` [PATCH bpf-next 07/10] bpf: btf: Add pretty print support to the basic arraymap Martin KaFai Lau
2018-03-31 9:12 ` kbuild test robot [this message]
2018-03-31 15:45 ` Martin KaFai Lau
2018-03-31 9:12 ` [RFC PATCH] bpf: btf: map_seq_next() can be static kbuild test robot
2018-03-30 18:26 ` [PATCH bpf-next 08/10] bpf: btf: Sync bpf.h and btf.h to tools/ Martin KaFai Lau
2018-03-30 18:26 ` [PATCH bpf-next 09/10] bpf: btf: Add BTF support to libbpf Martin KaFai Lau
2018-03-30 18:26 ` [PATCH bpf-next 10/10] bpf: btf: Add BTF tests Martin KaFai Lau
2018-04-03 19:30 ` [PATCH bpf-next 00/10] BTF: BPF Type Format Arnaldo Carvalho de Melo
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=201803311609.tsZ62eCl%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=kbuild-all@01.org \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
/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).