From: kbuild test robot <lkp@intel.com>
To: fgao@ikuai8.com
Cc: kbuild-all@01.org, davem@davemloft.net, maheshb@google.com,
edumazet@google.com, netdev@vger.kernel.org,
gfree.wind@gmail.com, Gao Feng <fgao@ikuai8.com>
Subject: Re: [PATCH net-next 1/1] driver: ipvlan: Use NF_IP_PRI_LAST as hook priority instead of INT_MAX
Date: Sun, 27 Nov 2016 19:17:29 +0800 [thread overview]
Message-ID: <201611271927.VjauNPub%fengguang.wu@intel.com> (raw)
In-Reply-To: <1480242245-7516-1-git-send-email-fgao@ikuai8.com>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
Hi Gao,
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/fgao-ikuai8-com/driver-ipvlan-Use-NF_IP_PRI_LAST-as-hook-priority-instead-of-INT_MAX/20161127-182724
config: x86_64-allmodconfig (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 >>):
>> drivers/net/ipvlan/ipvlan_main.c:19:15: error: 'NF_IP_PRI_LAST' undeclared here (not in a function)
.priority = NF_IP_PRI_LAST,
^~~~~~~~~~~~~~
vim +/NF_IP_PRI_LAST +19 drivers/net/ipvlan/ipvlan_main.c
13
14 static struct nf_hook_ops ipvl_nfops[] __read_mostly = {
15 {
16 .hook = ipvlan_nf_input,
17 .pf = NFPROTO_IPV4,
18 .hooknum = NF_INET_LOCAL_IN,
> 19 .priority = NF_IP_PRI_LAST,
20 },
21 {
22 .hook = ipvlan_nf_input,
---
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: 56839 bytes --]
next prev parent reply other threads:[~2016-11-27 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 10:24 [PATCH net-next 1/1] driver: ipvlan: Use NF_IP_PRI_LAST as hook priority instead of INT_MAX fgao
2016-11-27 11:17 ` kbuild test robot [this message]
2016-11-27 11:20 ` Gao Feng
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=201611271927.VjauNPub%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fgao@ikuai8.com \
--cc=gfree.wind@gmail.com \
--cc=kbuild-all@01.org \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.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