[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170215.222746.1747689327951875592.davem@davemloft.net>
Date: Wed, 15 Feb 2017 22:27:46 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: ast@...com
Cc: sfr@...b.auug.org.au, netdev@...r.kernel.org,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
peterz@...radead.org, mingo@...hat.com, acme@...nel.org,
alexander.shishkin@...ux.intel.com, joe@....org, jolsa@...hat.com
Subject: Re: linux-next: build failure after merge of the net tree
From: Alexei Starovoitov <ast@...com>
Date: Wed, 15 Feb 2017 19:06:02 -0800
> On 2/15/17 7:02 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> On Tue, 14 Feb 2017 09:12:50 +1100 Stephen Rothwell
>> <sfr@...b.auug.org.au> wrote:
>>>
>>> After merging the net tree, today's linux-next build (powerpc64le
>>> perf)
>>> failed like this:
>>>
>>> Warning: tools/include/uapi/linux/bpf.h differs from kernel
>>> bpf.c: In function 'bpf_prog_attach':
>>> bpf.c:180:6: error: 'union bpf_attr' has no member named
>>> 'attach_flags'; did you mean 'map_flags'?
>>> attr.attach_flags = flags;
>>> ^
>>>
>>> Caused by commit
>>>
>>> 7f677633379b ("bpf: introduce BPF_F_ALLOW_OVERRIDE flag")
>>>
>>
>> So do we have a fix for this? I am sure that Dave would like to send
>> his "net" tree to Linus sometime soonish ...
>
> Do you mind resending it to netdev with my Ack ?
> please mention [PATCH net] in subj, so it's get caught by Dave's
> scripts.
I applied the fix that synced the two header files already.
Powered by blists - more mailing lists