[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180331154549.qx3nbsmyksxon4hq@kafai-mbp>
Date: Sat, 31 Mar 2018 08:45:51 -0700
From: Martin KaFai Lau <kafai@...com>
To: kbuild test robot <lkp@...el.com>
CC: <kbuild-all@...org>, <netdev@...r.kernel.org>,
Alexei Starovoitov <ast@...com>,
Daniel Borkmann <daniel@...earbox.net>, <kernel-team@...com>
Subject: Re: [PATCH bpf-next 01/10] bpf: btf: Introduce BPF Type Format (BTF)
On Sat, Mar 31, 2018 at 04:43:28PM +0800, kbuild test robot wrote:
> 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/btf.c:666:28: sparse: symbol 'enum_ops' was not declared. Should it be static?
Will fix.
> kernel/bpf/btf.c:833:20: warning: 'btf_parse' defined but not used [-Wunused-function]
> static struct btf *btf_parse(void __user *btf_data, u32 btf_data_size,
> ^~~~~~~~~
>
> Please review and possibly fold the followup patch.
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.01.org_pipermail_kbuild-2Dall&d=DwIBAg&c=5VD0RTtNlTh3ycd41b3MUw&r=i6WobKxbeG3slzHSIOxTVtYIJw7qjCE6S0spDTKL-J4&m=BAJUulTMHXjeEr1-VzmmArWTyy-jw6EQCpXcfu55F24&s=0ONTIfdCBBkwhZYybgLYnml6UxfBXv2XBDjxtAsF1uc&e= Intel Corporation
Powered by blists - more mailing lists