From: kbuild test robot <lkp@intel.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: kbuild-all@01.org, network dev <netdev@vger.kernel.org>,
netfilter-devel@vger.kernel.org, davem@davemloft.net,
pablo@netfilter.org, Hans Schillstrom <hans@schillstrom.com>
Subject: Re: [PATCH net] ipvs: call ip_vs_dst_notifier before ipv6_dev_notf
Date: Wed, 14 Nov 2018 12:38:20 +0800 [thread overview]
Message-ID: <201811141232.H4SG8SzP%fengguang.wu@intel.com> (raw)
In-Reply-To: <4bfc74f2a94e3721afd5ee4dd3cb60f8e4b68c7c.1542129933.git.lucien.xin@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
Hi Xin,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on net/master]
url: https://github.com/0day-ci/linux/commits/Xin-Long/ipvs-call-ip_vs_dst_notifier-before-ipv6_dev_notf/20181114-055727
config: i386-randconfig-x005-11131818 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> net/netfilter/ipvs/ip_vs_ctl.c:3983:14: error: 'ADDRCONF_NOTIFY_PRIORITY' undeclared here (not in a function); did you mean 'DEVCONF_NDISC_NOTIFY'?
.priority = ADDRCONF_NOTIFY_PRIORITY + 5,
^~~~~~~~~~~~~~~~~~~~~~~~
DEVCONF_NDISC_NOTIFY
vim +3983 net/netfilter/ipvs/ip_vs_ctl.c
3980
3981 static struct notifier_block ip_vs_dst_notifier = {
3982 .notifier_call = ip_vs_dst_event,
> 3983 .priority = ADDRCONF_NOTIFY_PRIORITY + 5,
3984 };
3985
---
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: 33999 bytes --]
next prev parent reply other threads:[~2018-11-14 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 17:25 [PATCH net] ipvs: call ip_vs_dst_notifier before ipv6_dev_notf Xin Long
2018-11-13 19:51 ` Julian Anastasov
2018-11-14 4:38 ` kbuild test robot [this message]
2018-11-14 15:08 ` Xin Long
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=201811141232.H4SG8SzP%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=hans@schillstrom.com \
--cc=kbuild-all@01.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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