2:41 a.m.
Hi Alexei,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on bpf-next/master]
url:
https://github.com/0day-ci/linux/commits/Alexei-Starovoitov/bpf-Introduce...
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: i386-randconfig-s001-20210522 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
#
https://github.com/0day-ci/linux/commit/9380db20bb780c2f5147a795ac7f5fc13...
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review
Alexei-Starovoitov/bpf-Introduce-bpf_timer/20210522-204413
git checkout 9380db20bb780c2f5147a795ac7f5fc133f66d55
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp(a)intel.com>
sparse warnings: (new ones prefixed by >>)
> kernel/bpf/helpers.c:1030:29: sparse: sparse: symbol
'bpf_timer_init_proto' was not declared. Should it be static?
> kernel/bpf/helpers.c:1056:29: sparse: sparse: symbol 'bpf_timer_mod_proto'
was not declared. Should it be static?
> kernel/bpf/helpers.c:1081:29: sparse: sparse: symbol 'bpf_timer_del_proto'
was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
486
days inactive
486
days old
0 comments
1 participants
participants (1)
-
kernel test robot