From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com ([209.132.183.28]:36748 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932694AbcI3Nao (ORCPT ); Fri, 30 Sep 2016 09:30:44 -0400 From: Aaron Conole To: David Miller , Pablo Neira Ayuso Cc: kvalo@codeaurora.org, linux-wireless@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: pull-request: wireless-drivers-next 2016-09-29 References: <87ponmve2v.fsf@kamboji.qca.qualcomm.com> <20160930.013245.1474369794552343595.davem@davemloft.net> Date: Fri, 30 Sep 2016 09:30:40 -0400 In-Reply-To: <20160930.013245.1474369794552343595.davem@davemloft.net> (David Miller's message of "Fri, 30 Sep 2016 01:32:45 -0400 (EDT)") Message-ID: (sfid-20160930_153143_023896_419784BB) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-wireless-owner@vger.kernel.org List-ID: David Miller writes: > From: Kalle Valo > 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.