From: kbuild test robot <lkp@intel.com>
To: Tom Herbert <tom@quantonium.net>
Cc: kbuild-all@01.org, davem@davemloft.net, netdev@vger.kernel.org,
roopa@cumulusnetworks.com, rohit@quantonium.net,
Tom Herbert <tom@quantonium.net>
Subject: Re: [PATCH v4 net-next 3/6] ila: Call library function alloc_bucket_locks
Date: Sun, 17 Dec 2017 04:47:21 +0800 [thread overview]
Message-ID: <201712170446.COuJMOQI%fengguang.wu@intel.com> (raw)
In-Reply-To: <20171215182800.10248-4-tom@quantonium.net>
[-- Attachment #1: Type: text/plain, Size: 1981 bytes --]
Hi Tom,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/Tom-Herbert/net-ILA-notification-mechanism-and-fixes/20171217-041013
config: x86_64-randconfig-x019-201751 (attached as .config)
compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
Note: the linux-review/Tom-Herbert/net-ILA-notification-mechanism-and-fixes/20171217-041013 HEAD bdefe11e33bb3662a60476ea17663189974227a0 builds fine.
It only hurts bisectibility.
All error/warnings (new ones prefixed by >>):
net/ipv6/ila/ila_xlat.c: In function 'alloc_ila_locks':
>> net/ipv6/ila/ila_xlat.c:39:37: error: 'struct ila_net' has no member named 'xlat'
return alloc_bucket_spinlocks(&ilan->xlat.locks, &ilan->xlat.locks_mask,
^~
net/ipv6/ila/ila_xlat.c:39:56: error: 'struct ila_net' has no member named 'xlat'
return alloc_bucket_spinlocks(&ilan->xlat.locks, &ilan->xlat.locks_mask,
^~
net/ipv6/ila/ila_xlat.c: In function 'ila_exit_net':
net/ipv6/ila/ila_xlat.c:630:28: error: 'struct ila_net' has no member named 'xlat'
free_bucket_spinlocks(ilan->xlat.locks);
^~
net/ipv6/ila/ila_xlat.c: In function 'alloc_ila_locks':
>> net/ipv6/ila/ila_xlat.c:42:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
vim +39 net/ipv6/ila/ila_xlat.c
36
37 static int alloc_ila_locks(struct ila_net *ilan)
38 {
> 39 return alloc_bucket_spinlocks(&ilan->xlat.locks, &ilan->xlat.locks_mask,
40 MAX_LOCKS, LOCKS_PER_CPU,
41 GFP_KERNEL);
> 42 }
43
---
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: 31625 bytes --]
next prev parent reply other threads:[~2017-12-16 20:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 18:27 [PATCH v4 net-next 0/6] net: ILA notification mechanism and fixes Tom Herbert
2017-12-15 18:27 ` [PATCH v4 net-next 1/6] lwt: Add net to build_state argument Tom Herbert
2017-12-19 15:47 ` Roopa Prabhu
2017-12-15 18:27 ` [PATCH v4 net-next 2/6] ila: Fix use of rhashtable walk in ila_xlat.c Tom Herbert
2017-12-15 18:27 ` [PATCH v4 net-next 3/6] ila: Call library function alloc_bucket_locks Tom Herbert
2017-12-16 20:47 ` kbuild test robot [this message]
2017-12-15 18:27 ` [PATCH v4 net-next 4/6] ila: create main ila source file Tom Herbert
2017-12-15 18:27 ` [PATCH v4 net-next 5/6] ila: Flush netlink command to clear xlat table Tom Herbert
2017-12-15 18:28 ` [PATCH v4 net-next 6/6] ila: Route notify Tom Herbert
2017-12-16 22:18 ` [RFC PATCH] ila: ila_notify() can be static kbuild test robot
2017-12-16 22:18 ` [PATCH v4 net-next 6/6] ila: Route notify kbuild test robot
2017-12-19 16:28 ` 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=201712170446.COuJMOQI%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=rohit@quantonium.net \
--cc=roopa@cumulusnetworks.com \
--cc=tom@quantonium.net \
/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;
as well as URLs for NNTP newsgroup(s).