From: kbuild test robot <lkp@intel.com>
To: Mathieu Xhonneux <m.xhonneux@gmail.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org, dlebrun@google.com,
alexei.starovoitov@gmail.com
Subject: Re: [PATCH bpf-next v3 3/6] bpf: Add IPv6 Segment Routing helpers
Date: Mon, 7 May 2018 07:29:23 +0800 [thread overview]
Message-ID: <201805070716.KC2OLOyD%fengguang.wu@intel.com> (raw)
In-Reply-To: <afdb283dc01972faa04020bdc50798297010c8a1.1525626429.git.m.xhonneux@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]
Hi Mathieu,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on bpf-next/master]
url: https://github.com/0day-ci/linux/commits/Mathieu-Xhonneux/ipv6-sr-introduce-seg6local-End-BPF-action/20180506-233046
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: s390-allmodconfig (attached as .config)
compiler: s390x-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=s390
All errors (new ones prefixed by >>):
net/core/filter.o: In function `bpf_push_seg6_encap':
filter.c:(.text+0xaf4c): undefined reference to `seg6_validate_srh'
filter.c:(.text+0xaf8a): undefined reference to `seg6_do_srh_inline'
filter.c:(.text+0xafc4): undefined reference to `seg6_do_srh_encap'
filter.c:(.text+0xb016): undefined reference to `seg6_lookup_nexthop'
net/core/filter.o: In function `bpf_lwt_seg6_store_bytes':
>> (.text+0xb106): undefined reference to `seg6_bpf_srh_states'
net/core/filter.o: In function `bpf_lwt_seg6_action':
(.text+0xb2b0): undefined reference to `seg6_bpf_srh_states'
>> (.text+0xb334): undefined reference to `seg6_validate_srh'
>> (.text+0xb394): undefined reference to `seg6_lookup_nexthop'
(.text+0xb3c4): undefined reference to `seg6_lookup_nexthop'
net/core/filter.o: In function `bpf_lwt_seg6_adjust_srh':
(.text+0xb492): undefined reference to `seg6_bpf_srh_states'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 49312 bytes --]
next prev parent reply other threads:[~2018-05-06 23:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 17:27 [PATCH bpf-next v3 0/6] ipv6: sr: introduce seg6local End.BPF action Mathieu Xhonneux
2018-05-06 17:27 ` [PATCH bpf-next v3 1/6] ipv6: sr: make seg6.h includable without IPv6 Mathieu Xhonneux
2018-05-06 17:27 ` [PATCH bpf-next v3 2/6] ipv6: sr: export function lookup_nexthop Mathieu Xhonneux
2018-05-06 17:27 ` [PATCH bpf-next v3 3/6] bpf: Add IPv6 Segment Routing helpers Mathieu Xhonneux
2018-05-06 23:29 ` kbuild test robot [this message]
2018-05-07 22:21 ` Mathieu Xhonneux
2018-05-09 1:57 ` Alexei Starovoitov
2018-05-06 23:50 ` kbuild test robot
2018-05-06 17:27 ` [PATCH bpf-next v3 4/6] bpf: Split lwt inout verifier structures Mathieu Xhonneux
2018-05-06 17:27 ` [PATCH bpf-next v3 5/6] ipv6: sr: Add seg6local action End.BPF Mathieu Xhonneux
2018-05-06 17:27 ` [PATCH bpf-next v3 6/6] selftests/bpf: test for seg6local End.BPF action Mathieu Xhonneux
2018-05-07 1:33 ` [PATCH bpf-next v3 0/6] ipv6: sr: introduce " Alexei Starovoitov
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=201805070716.KC2OLOyD%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=alexei.starovoitov@gmail.com \
--cc=dlebrun@google.com \
--cc=kbuild-all@01.org \
--cc=m.xhonneux@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.