Netdev List
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
	roopa@cumulusnetworks.com, dsa@cumulusnetworks.com,
	mrv@mojatatu.com, stephen@networkplumber.org,
	bridge@lists.linux-foundation.org,
	Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Subject: Re: [PATCH net-next v2 2/2] bridge: vlan: signal if anything changed on vlan add
Date: Thu, 26 Oct 2017 04:51:12 +0800	[thread overview]
Message-ID: <201710260418.YKhNnusJ%fengguang.wu@intel.com> (raw)
In-Reply-To: <1508848362-13750-3-git-send-email-nikolay@cumulusnetworks.com>

[-- Attachment #1: Type: text/plain, Size: 2656 bytes --]

Hi Nikolay,

[auto build test ERROR on net-next/master]

url:    https://github.com/0day-ci/linux/commits/Nikolay-Aleksandrov/bridge-make-setlink-dellink-notifications-more-accurate/20171026-042029
config: x86_64-randconfig-x019-201743 (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/bridge/br_netlink.c: In function 'br_vlan_info':
>> net/bridge/br_netlink.c:520:10: error: too many arguments to function 'nbp_vlan_add'
       err = nbp_vlan_add(p, vinfo->vid, vinfo->flags,
             ^~~~~~~~~~~~
   In file included from net/bridge/br_netlink.c:21:0:
   net/bridge/br_private.h:931:19: note: declared here
    static inline int nbp_vlan_add(struct net_bridge_port *port, u16 vid, u16 flags)
                      ^~~~~~~~~~~~
>> net/bridge/br_netlink.c:524:10: error: too many arguments to function 'br_vlan_add'
       err = br_vlan_add(br, vinfo->vid, vinfo->flags,
             ^~~~~~~~~~~
   In file included from net/bridge/br_netlink.c:21:0:
   net/bridge/br_private.h:908:19: note: declared here
    static inline int br_vlan_add(struct net_bridge *br, u16 vid, u16 flags)
                      ^~~~~~~~~~~

vim +/nbp_vlan_add +520 net/bridge/br_netlink.c

   507	
   508	static int br_vlan_info(struct net_bridge *br, struct net_bridge_port *p,
   509				int cmd, struct bridge_vlan_info *vinfo, bool *changed)
   510	{
   511		bool curr_change;
   512		int err = 0;
   513	
   514		switch (cmd) {
   515		case RTM_SETLINK:
   516			if (p) {
   517				/* if the MASTER flag is set this will act on the global
   518				 * per-VLAN entry as well
   519				 */
 > 520				err = nbp_vlan_add(p, vinfo->vid, vinfo->flags,
   521						   &curr_change);
   522			} else {
   523				vinfo->flags |= BRIDGE_VLAN_INFO_BRENTRY;
 > 524				err = br_vlan_add(br, vinfo->vid, vinfo->flags,
   525						  &curr_change);
   526			}
   527			if (curr_change)
   528				*changed = true;
   529			break;
   530	
   531		case RTM_DELLINK:
   532			if (p) {
   533				if (!nbp_vlan_delete(p, vinfo->vid))
   534					*changed = true;
   535	
   536				if ((vinfo->flags & BRIDGE_VLAN_INFO_MASTER) &&
   537				    !br_vlan_delete(p->br, vinfo->vid))
   538					*changed = true;
   539			} else if (!br_vlan_delete(br, vinfo->vid)) {
   540				*changed = true;
   541			}
   542			break;
   543		}
   544	
   545		return err;
   546	}
   547	

---
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: 21550 bytes --]

  reply	other threads:[~2017-10-25 20:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 12:32 [PATCH net-next v2 0/2] bridge: make setlink/dellink notifications more accurate Nikolay Aleksandrov
2017-10-24 12:32 ` [PATCH net-next v2 1/2] bridge: netlink: " Nikolay Aleksandrov
2017-10-24 12:32 ` [PATCH net-next v2 2/2] bridge: vlan: signal if anything changed on vlan add Nikolay Aleksandrov
2017-10-25 20:51   ` kbuild test robot [this message]
2017-10-25 21:49 ` [PATCH net-next v2 0/2] bridge: make setlink/dellink notifications more accurate Nikolay Aleksandrov
2017-10-25 21:59   ` [PATCH net-next v3 " Nikolay Aleksandrov
2017-10-25 21:59     ` [PATCH net-next v3 1/2] bridge: netlink: " Nikolay Aleksandrov
2017-10-26  8:17       ` Stephen Hemminger
2017-10-26  8:25         ` Nikolay Aleksandrov
2017-10-25 21:59     ` [PATCH net-next v3 2/2] bridge: vlan: signal if anything changed on vlan add Nikolay Aleksandrov
2017-10-25 22:14     ` [PATCH net-next v3 0/2] bridge: make setlink/dellink notifications more accurate Nikolay Aleksandrov
2017-10-25 22:52       ` [PATCH net-next v4 " Nikolay Aleksandrov
2017-10-25 22:52         ` [PATCH net-next v4 1/2] bridge: netlink: " Nikolay Aleksandrov
2017-10-25 22:52         ` [PATCH net-next v4 2/2] bridge: vlan: signal if anything changed on vlan add Nikolay Aleksandrov
2017-10-26 10:16           ` Toshiaki Makita
2017-10-26 11:02             ` [Bridge] " Nikolay Aleksandrov
2017-10-26 11:08               ` Nikolay Aleksandrov
2017-10-26  1:12       ` [PATCH net-next v3 0/2] bridge: make setlink/dellink notifications more accurate David Miller

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=201710260418.YKhNnusJ%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=dsa@cumulusnetworks.com \
    --cc=kbuild-all@01.org \
    --cc=mrv@mojatatu.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=roopa@cumulusnetworks.com \
    --cc=stephen@networkplumber.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