Netdev List
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Roopa Prabhu <roopa@cumulusnetworks.com>
Cc: kbuild-all@01.org, davem@davemloft.net,
	stephen@networkplumber.org, nikolay@cumulusnetworks.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next] bridge: set is_local and is_static before fdb entry is added to the fdb hashtable
Date: Tue, 27 Oct 2015 12:16:51 +0800	[thread overview]
Message-ID: <201510271206.HPbBjdTp%fengguang.wu@intel.com> (raw)
In-Reply-To: <1445918676-45416-1-git-send-email-roopa@cumulusnetworks.com>

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

Hi Roopa,

[auto build test ERROR on net-next/master -- if it's inappropriate base, please suggest rules for selecting the more suitable base]

url:    https://github.com/0day-ci/linux/commits/Roopa-Prabhu/bridge-set-is_local-and-is_static-before-fdb-entry-is-added-to-the-fdb-hashtable/20151027-120635
config: i386-randconfig-x009-201543 (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   net/bridge/br_fdb.c: In function 'br_fdb_external_learn_add':
>> net/bridge/br_fdb.c:1103:9: error: too few arguments to function 'fdb_create'
      fdb = fdb_create(head, p, addr, vid);
            ^
   net/bridge/br_fdb.c:495:37: note: declared here
    static struct net_bridge_fdb_entry *fdb_create(struct hlist_head *head,
                                        ^

vim +/fdb_create +1103 net/bridge/br_fdb.c

3aeb6617 Jiri Pirko    2015-01-15  1097  	ASSERT_RTNL();
cf6b8e1e Scott Feldman 2014-11-28  1098  	spin_lock_bh(&br->hash_lock);
cf6b8e1e Scott Feldman 2014-11-28  1099  
cf6b8e1e Scott Feldman 2014-11-28  1100  	head = &br->hash[br_mac_hash(addr, vid)];
cf6b8e1e Scott Feldman 2014-11-28  1101  	fdb = fdb_find(head, addr, vid);
cf6b8e1e Scott Feldman 2014-11-28  1102  	if (!fdb) {
cf6b8e1e Scott Feldman 2014-11-28 @1103  		fdb = fdb_create(head, p, addr, vid);
cf6b8e1e Scott Feldman 2014-11-28  1104  		if (!fdb) {
cf6b8e1e Scott Feldman 2014-11-28  1105  			err = -ENOMEM;
cf6b8e1e Scott Feldman 2014-11-28  1106  			goto err_unlock;

:::::: The code at line 1103 was first introduced by commit
:::::: cf6b8e1eedffd9ef9a22c0c9453d752b07daf89a bridge: add API to notify bridge driver of learned FBD on offloaded device

:::::: TO: Scott Feldman <sfeldma@gmail.com>
:::::: CC: David S. Miller <davem@davemloft.net>

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 26664 bytes --]

  reply	other threads:[~2015-10-27  4:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27  4:04 [PATCH net-next] bridge: set is_local and is_static before fdb entry is added to the fdb hashtable Roopa Prabhu
2015-10-27  4:16 ` kbuild test robot [this message]
2015-10-27 12:06   ` roopa

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=201510271206.HPbBjdTp%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=davem@davemloft.net \
    --cc=kbuild-all@01.org \
    --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