From: Roopa Prabhu <roopa@cumulusnetworks.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org, davem@davemloft.net,
stephen@networkplumber.org, nikolay@cumulusnetworks.com,
tgraf@suug.ch, hannes@stressinduktion.org, jbenc@redhat.com,
pshelar@ovn.org, dsa@cumulusnetworks.com, hadi@mojatatu.com
Subject: Re: [PATCH net-next 5/5] bridge: vlan dst_metadata hooks in ingress and egress paths
Date: Tue, 31 Jan 2017 07:38:33 -0800 [thread overview]
Message-ID: <5890AF79.4070801@cumulusnetworks.com> (raw)
In-Reply-To: <201701312023.j4hsk5qZ%fengguang.wu@intel.com>
On 1/31/17, 4:52 AM, kbuild test robot wrote:
> Hi Roopa,
>
> [auto build test ERROR on net-next/master]
>
> url: https://github.com/0day-ci/linux/commits/Roopa-Prabhu/bridge-per-vlan-dst_metadata-support/20170131-140750
> config: x86_64-allyesdebian (attached as .config)
> compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
> net/built-in.o: In function `br_handle_frame':
>>> (.text+0x1bb3ca): undefined reference to `br_handle_ingress_vlan_tunnel'
> net/built-in.o: In function `br_setport':
> br_netlink.c:(.text+0x1be953): undefined reference to `nbp_vlan_tunnel_info_flush'
> net/built-in.o: In function `br_vlan_tunnel_info':
> br_netlink_tunnel.c:(.text+0x1bfc24): undefined reference to `nbp_vlan_tunnel_info_add'
> br_netlink_tunnel.c:(.text+0x1bfc2f): undefined reference to `nbp_vlan_tunnel_info_delete'
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
Thanks and sorry abt these. will send v2 with fix for these and other reported warnings with CONFIG_BRIDGE VLAN_FILTERING off.
next prev parent reply other threads:[~2017-01-31 15:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 5:57 [PATCH net-next 0/5] bridge: per vlan dst_metadata support Roopa Prabhu
2017-01-31 5:57 ` [PATCH net-next 1/5] ip_tunnels: new IP_TUNNEL_INFO_BRIDGE flag for ip_tunnel_info mode Roopa Prabhu
2017-01-31 5:57 ` [PATCH net-next 2/5] vxlan: support fdb and learning in COLLECT_METADATA mode Roopa Prabhu
2017-01-31 23:37 ` Jonathan Toppins
2017-02-01 3:38 ` Roopa Prabhu
2017-01-31 5:57 ` [PATCH net-next 3/5] bridge: uapi: add per vlan tunnel info Roopa Prabhu
2017-01-31 5:57 ` [PATCH net-next 4/5] bridge: per vlan dst_metadata netlink support Roopa Prabhu
2017-01-31 7:12 ` kbuild test robot
2017-01-31 9:34 ` kbuild test robot
2017-01-31 5:57 ` [PATCH net-next 5/5] bridge: vlan dst_metadata hooks in ingress and egress paths Roopa Prabhu
2017-01-31 12:52 ` kbuild test robot
2017-01-31 15:38 ` Roopa Prabhu [this message]
2017-01-31 16:41 ` [PATCH net-next 0/5] bridge: per vlan dst_metadata support Stephen Hemminger
2017-01-31 20:43 ` Roopa Prabhu
2017-02-01 16:35 ` Stephen Hemminger
2017-02-01 19:12 ` Roopa Prabhu
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=5890AF79.4070801@cumulusnetworks.com \
--to=roopa@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=hadi@mojatatu.com \
--cc=hannes@stressinduktion.org \
--cc=jbenc@redhat.com \
--cc=kbuild-all@01.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=pshelar@ovn.org \
--cc=stephen@networkplumber.org \
--cc=tgraf@suug.ch \
/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.