From: Martin KaFai Lau <kafai@fb.com>
To: David Miller <davem@davemloft.net>
Cc: <fengguang.wu@intel.com>, <kbuild-all@01.org>, <netdev@vger.kernel.org>
Subject: Re: [net-next:master 1184/1189] include/linux/bpf.h:324:21: error: 'NUMA_NO_NODE' undeclared
Date: Sat, 19 Aug 2017 23:44:35 -0700 [thread overview]
Message-ID: <20170820064435.condwbct5aqeufut@kafai-mba.local> (raw)
In-Reply-To: <20170819.233313.2054468070616685885.davem@davemloft.net>
On Sat, Aug 19, 2017 at 11:33:13PM -0700, David Miller wrote:
> From: kbuild test robot <fengguang.wu@intel.com>
> Date: Sun, 20 Aug 2017 13:43:54 +0800
>
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
> > head: 228498596c44041c710f5a633904205bc1cd9177
> > commit: 96eabe7a40aa17e613cf3db2c742ee8b1fc764d0 [1184/1189] bpf: Allow selecting numa node during map creation
> > config: i386-randconfig-s1-201734 (attached as .config)
> > compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
> > reproduce:
> > git checkout 96eabe7a40aa17e613cf3db2c742ee8b1fc764d0
> > # save the attached .config to linux build tree
> > make ARCH=i386
> >
> > All error/warnings (new ones prefixed by >>):
> >
> > In file included from net/bpf/test_run.c:7:0:
> > include/linux/bpf.h: In function 'bpf_map_attr_numa_node':
> >>> include/linux/bpf.h:324:21: error: 'NUMA_NO_NODE' undeclared (first use in this function)
> > attr->numa_node : NUMA_NO_NODE;
> > ^~~~~~~~~~~~
>
> I'll add the linux/numa.h include to linux/bpf.h
Thanks for fixing it. Sorry for the mistake.
prev parent reply other threads:[~2017-08-20 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 5:43 [net-next:master 1184/1189] include/linux/bpf.h:324:21: error: 'NUMA_NO_NODE' undeclared kbuild test robot
2017-08-20 6:27 ` Martin KaFai Lau
2017-08-20 6:33 ` David Miller
2017-08-20 6:44 ` Martin KaFai Lau [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=20170820064435.condwbct5aqeufut@kafai-mba.local \
--to=kafai@fb.com \
--cc=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--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