From: kbuild test robot <lkp@intel.com>
To: Tom Herbert <tom@quantonium.net>
Cc: kbuild-all@01.org, netdev@vger.kernel.org, rohit@quantonium.net,
davejwatson@fb.com, Tom Herbert <tom@quantonium.net>
Subject: Re: [PATCH net-next 2/4] sock: ULP infrastructure
Date: Wed, 2 Aug 2017 15:52:51 +0800 [thread overview]
Message-ID: <201708021533.eau5MA08%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170802025304.1862-3-tom@quantonium.net>
[-- Attachment #1: Type: text/plain, Size: 2351 bytes --]
Hi Tom,
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/Tom-Herbert/ulp-Generalize-ULP-infrastructure/20170802-142035
config: x86_64-rhel (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 >>):
In file included from include/net/sock.h:75:0,
from include/net/inet_sock.h:27,
from include/net/ip.h:30,
from drivers/net/ethernet/broadcom/cnic.c:37:
include/net/ulp_sock.h:51:1: error: expected identifier or '(' before '{' token
{
^
include/net/ulp_sock.h:56:1: error: expected identifier or '(' before '{' token
{
^
include/net/ulp_sock.h:60:1: error: expected identifier or '(' before '{' token
{
^
>> drivers/net/ethernet/broadcom/cnic.c:178:20: error: conflicting types for 'ulp_get'
static inline void ulp_get(struct cnic_ulp_ops *ulp_ops)
^~~~~~~
In file included from include/net/sock.h:75:0,
from include/net/inet_sock.h:27,
from include/net/ip.h:30,
from drivers/net/ethernet/broadcom/cnic.c:37:
include/net/ulp_sock.h:50:5: note: previous declaration of 'ulp_get' was here
int ulp_get(struct sock *sk, char __user *optval, int *optlen);
^~~~~~~
vim +/ulp_get +178 drivers/net/ethernet/broadcom/cnic.c
a4636960 drivers/net/cnic.c Michael Chan 2009-06-08 177
7fc1ece4 drivers/net/cnic.c Michael Chan 2009-08-14 @178 static inline void ulp_get(struct cnic_ulp_ops *ulp_ops)
7fc1ece4 drivers/net/cnic.c Michael Chan 2009-08-14 179 {
7fc1ece4 drivers/net/cnic.c Michael Chan 2009-08-14 180 atomic_inc(&ulp_ops->ref_count);
7fc1ece4 drivers/net/cnic.c Michael Chan 2009-08-14 181 }
7fc1ece4 drivers/net/cnic.c Michael Chan 2009-08-14 182
:::::: The code at line 178 was first introduced by commit
:::::: 7fc1ece40704b150477e548a7a98d285cc418790 cnic: Fix locking in init/exit calls.
:::::: TO: Michael Chan <mchan@broadcom.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/gzip, Size: 39621 bytes --]
next prev parent reply other threads:[~2017-08-02 7:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 2:53 [PATCH net-next 0/4] ulp: Generalize ULP infrastructure Tom Herbert
2017-08-02 2:53 ` [PATCH net-next 1/4] inet: include net/sock.h in inet_common.h Tom Herbert
2017-08-02 2:53 ` [PATCH net-next 2/4] sock: ULP infrastructure Tom Herbert
2017-08-02 7:32 ` kbuild test robot
2017-08-02 7:52 ` kbuild test robot [this message]
2017-08-02 2:53 ` [PATCH net-next 3/4] tcp: Adjust TCP ULP to defer to sockets ULP Tom Herbert
2017-08-02 2:53 ` [PATCH net-next 4/4] ulp: Documention for ULP infrastructure Tom Herbert
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=201708021533.eau5MA08%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davejwatson@fb.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=rohit@quantonium.net \
--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