linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: NetFilter <netfilter-devel@vger.kernel.org>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the netfilter-next tree
Date: Tue, 2 Jan 2018 16:30:01 +0100	[thread overview]
Message-ID: <20180102153001.34ot5wwfwbgdkumy@salvia> (raw)
In-Reply-To: <20180102121451.3f8f792d@canb.auug.org.au>

Hi Stephen,

On Tue, Jan 02, 2018 at 12:14:51PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the netfilter-next tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> In file included from net/ipv6/af_inet6.c:45:0:
> include/linux/netfilter_ipv6.h:38:51: warning: 'struct nf_queue_entry' declared inside parameter list
>   int (*reroute)(struct sk_buff *skb, const struct nf_queue_entry *entry);
>                                                    ^

Arnd sent a fix for this, thanks for reporting!

https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git/commit/

  reply	other threads:[~2018-01-02 15:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-02  1:14 linux-next: build warning after merge of the netfilter-next tree Stephen Rothwell
2018-01-02 15:30 ` Pablo Neira Ayuso [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-03-30  0:26 Stephen Rothwell
2018-05-07  0:55 Stephen Rothwell
2018-05-08  0:21 ` Stephen Rothwell
2018-05-08  7:17   ` Florian Westphal
2018-05-15 10:54     ` Geert Uytterhoeven
2018-05-15 17:51       ` Florian Westphal
2017-11-07  0:02 Stephen Rothwell
2017-11-08  8:00 ` Stephen Rothwell
2017-11-08 23:40   ` Pablo Neira Ayuso
2017-11-15 22:46     ` Stephen Rothwell
2017-11-16 14:18       ` Pablo Neira Ayuso
2017-11-16 20:46         ` Stephen Rothwell
2017-03-20  0:12 Stephen Rothwell
2017-03-20  7:00 ` Reshetova, Elena
2017-03-20  8:44   ` Stephen Rothwell

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=20180102153001.34ot5wwfwbgdkumy@salvia \
    --to=pablo@netfilter.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).