From: kbuild test robot <lkp@intel.com>
To: Marcel Apfelbaum <marcel@redhat.com>
Cc: kbuild-all@01.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, monis@mellanox.com,
dledford@redhat.com, sean.hefty@intel.com,
hal.rosenstock@gmail.com, marcel@redhat.com,
yuval.shaia@oracle.com
Subject: Re: [PATCH] drivers/rxe: improve rxe loopback
Date: Thu, 27 Jul 2017 21:47:24 +0800 [thread overview]
Message-ID: <201707272157.EUWbJG6R%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170726145248.21677-1-marcel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2204 bytes --]
Hi Marcel,
[auto build test ERROR on rdma/master]
[also build test ERROR on v4.13-rc2 next-20170727]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Marcel-Apfelbaum/drivers-rxe-improve-rxe-loopback/20170727-211514
base: https://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma.git master
config: i386-randconfig-x002-07271954 (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=i386
All error/warnings (new ones prefixed by >>):
drivers/infiniband/sw/rxe/rxe_net.c: In function 'addr6_same_rxe':
>> drivers/infiniband/sw/rxe/rxe_net.c:414:12: error: implicit declaration of function 'in6_dev_get' [-Werror=implicit-function-declaration]
in6_dev = in6_dev_get(rxe->ndev);
^~~~~~~~~~~
>> drivers/infiniband/sw/rxe/rxe_net.c:414:10: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
in6_dev = in6_dev_get(rxe->ndev);
^
>> drivers/infiniband/sw/rxe/rxe_net.c:426:2: error: implicit declaration of function 'in6_dev_put' [-Werror=implicit-function-declaration]
in6_dev_put(in6_dev);
^~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/in6_dev_get +414 drivers/infiniband/sw/rxe/rxe_net.c
407
408 static inline bool addr6_same_rxe(struct rxe_dev *rxe, struct in6_addr *daddr)
409 {
410 struct inet6_dev *in6_dev;
411 struct inet6_ifaddr *ifp;
412 bool same_rxe = false;
413
> 414 in6_dev = in6_dev_get(rxe->ndev);
415 if (!in6_dev)
416 return false;
417
418 read_lock_bh(&in6_dev->lock);
419 list_for_each_entry(ifp, &in6_dev->addr_list, if_list)
420 if (!memcmp(&ifp->addr, daddr, sizeof(*daddr))) {
421 same_rxe = true;
422 goto out;
423 }
424 out:
425 read_unlock_bh(&in6_dev->lock);
> 426 in6_dev_put(in6_dev);
427 return same_rxe;
428 }
429
---
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: 28776 bytes --]
prev parent reply other threads:[~2017-07-27 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 14:52 Marcel Apfelbaum
2017-07-26 19:36 ` Yuval Shaia
2017-07-26 19:56 ` Yuval Shaia
2017-07-26 19:57 ` Yuval Shaia
2017-07-27 7:04 ` Moni Shoua
2017-07-27 9:55 ` Marcel Apfelbaum
2017-07-30 9:57 ` Moni Shoua
2017-07-31 9:53 ` Marcel Apfelbaum
2017-07-27 7:36 ` Leon Romanovsky
2017-07-27 9:49 ` Marcel Apfelbaum
2017-07-27 10:40 ` Leon Romanovsky
2017-07-27 13:47 ` kbuild test robot [this message]
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=201707272157.EUWbJG6R%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dledford@redhat.com \
--cc=hal.rosenstock@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=marcel@redhat.com \
--cc=monis@mellanox.com \
--cc=sean.hefty@intel.com \
--cc=yuval.shaia@oracle.com \
/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
all inboxes | Powered by JetHome®