[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f7t4m4xtszj.fsf@redhat.com>
Date: Fri, 30 Sep 2016 09:30:40 -0400
From: Aaron Conole <aconole@...hat.com>
To: David Miller <davem@...emloft.net>,
Pablo Neira Ayuso <pablo@...filter.org>
Cc: kvalo@...eaurora.org, linux-wireless@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: pull-request: wireless-drivers-next 2016-09-29
David Miller <davem@...emloft.net> writes:
> From: Kalle Valo <kvalo@...eaurora.org>
> Date: Thu, 29 Sep 2016 19:57:28 +0300
>
...
>> Or actually I had one problem. While doing a test merge I noticed that
>> net-next fails to compile for me, but I don't think this is anything
>> wireless related:
>>
>> CC net/netfilter/core.o
>> net/netfilter/core.c: In function 'nf_set_hooks_head':
>> net/netfilter/core.c:96:149: error: 'struct net_device' has no
>> member named 'nf_hooks_ingress'
>
> Yes, I am aware of this build issue and will tackle it myself if someone
> doesn't beat me to it.
Sorry, I introduced this. I posted a series targetted at nf-next to
solve this, but it could be merged to net-next instead, if that makes
sense.
The patches are here:
https://patchwork.ozlabs.org/patch/676287/
https://patchwork.ozlabs.org/patch/676288/
Again, sorry for this.
Powered by blists - more mailing lists