From: Kalle Valo <kvalo@codeaurora.org>
To: Aaron Conole <aconole@redhat.com>
Cc: David Miller <davem@davemloft.net>,
Pablo Neira Ayuso <pablo@netfilter.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
Date: Wed, 05 Oct 2016 07:50:39 +0300 [thread overview]
Message-ID: <87bmyzpffk.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <f7t4m4xtszj.fsf@redhat.com> (Aaron Conole's message of "Fri, 30 Sep 2016 09:30:40 -0400")
Aaron Conole <aconole@redhat.com> writes:
> David Miller <davem@davemloft.net> writes:
>
>> From: Kalle Valo <kvalo@codeaurora.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/
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
next prev parent reply other threads:[~2016-10-05 4:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 16:57 pull-request: wireless-drivers-next 2016-09-29 Kalle Valo
2016-09-29 18:21 ` Pablo Neira Ayuso
2016-09-30 5:32 ` David Miller
2016-09-30 13:30 ` Aaron Conole
2016-10-05 4:50 ` Kalle Valo [this message]
2016-10-05 4:53 ` David Miller
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=87bmyzpffk.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.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