From: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
netdev@vger.kernel.org,
Jesper Dangaard Brouer <brouer@redhat.com>
Subject: Re: [PATCH bpf] xdp: Fix handling of devmap in generic XDP
Date: Thu, 14 Jun 2018 09:33:26 +0900 [thread overview]
Message-ID: <beece494-6942-3f96-bd55-e892fdd37a87@lab.ntt.co.jp> (raw)
In-Reply-To: <201806131752.fqIMeuHk%fengguang.wu@intel.com>
On 2018/06/13 18:27, kbuild test robot wrote:
> Hi Toshiaki,
>
> Thank you for the patch! Perhaps something to improve:
>
> [auto build test WARNING on bpf/master]
>
> url: https://github.com/0day-ci/linux/commits/Toshiaki-Makita/xdp-Fix-handling-of-devmap-in-generic-XDP/20180613-161204
> base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git master
> config: i386-randconfig-a1-201823 (attached as .config)
> compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All warnings (new ones prefixed by >>):
>
> In file included from net//bpf/test_run.c:7:0:
>>> include/linux/bpf.h:594:16: warning: 'struct sk_buff' declared inside parameter list
> struct bpf_prog *xdp_prog)
> ^
>>> include/linux/bpf.h:594:16: warning: its scope is only this definition or declaration, which is probably not what you want
>
> vim +594 include/linux/bpf.h
>
> 591
> 592 static inline int dev_map_generic_redirect(struct bpf_dtab_netdev *dst,
> 593 struct sk_buff *skb,
> > 594 struct bpf_prog *xdp_prog)
> 595 {
> 596 return 0;
> 597 }
> 598
Ugh I did build test for the entire tree with CONFIG_BPF_SYSCALL, and
net/core and kernel/bpf without CONFIG_BPF_SYSCALL but not net/bpf.
I'll make sure to test the entire tree next. will send v2.
--
Toshiaki Makita
prev parent reply other threads:[~2018-06-14 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 8:06 [PATCH bpf] xdp: Fix handling of devmap in generic XDP Toshiaki Makita
2018-06-13 8:51 ` kbuild test robot
2018-06-13 9:27 ` kbuild test robot
2018-06-14 0:33 ` Toshiaki Makita [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=beece494-6942-3f96-bd55-e892fdd37a87@lab.ntt.co.jp \
--to=makita.toshiaki@lab.ntt.co.jp \
--cc=ast@kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=kbuild-all@01.org \
--cc=lkp@intel.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