From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtp.codeaurora.org ([198.145.29.96]:39411 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751121AbcJEEuq (ORCPT ); Wed, 5 Oct 2016 00:50:46 -0400 From: Kalle Valo To: Aaron Conole Cc: David Miller , Pablo Neira Ayuso , 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: Wed, 05 Oct 2016 07:50:39 +0300 In-Reply-To: (Aaron Conole's message of "Fri, 30 Sep 2016 09:30:40 -0400") Message-ID: <87bmyzpffk.fsf@kamboji.qca.qualcomm.com> (sfid-20161005_065110_120102_20E82B53) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-wireless-owner@vger.kernel.org List-ID: Aaron Conole writes: > 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/ net-next still fails to compile for me. I verified that these two patches fix it but I don't see them in net-next yet. -- Kalle Valo