From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>, Networking <netdev@vger.kernel.org>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
NetFilter <netfilter-devel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Florian Westphal <fw@strlen.de>
Subject: Re: linux-next: build warning after merge of the netfilter-next tree
Date: Wed, 8 Nov 2017 19:00:52 +1100 [thread overview]
Message-ID: <20171108190052.63dfd8ce@canb.auug.org.au> (raw)
In-Reply-To: <20171107110248.7f1924a7@canb.auug.org.au>
Hi Dave,
On Tue, 7 Nov 2017 11:02:48 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the netfilter-next tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> net/netfilter/nf_conntrack_netlink.c:536:15: warning: 'ctnetlink_proto_size' defined but not used [-Wunused-function]
> static size_t ctnetlink_proto_size(const struct nf_conn *ct)
> ^
>
> Introduced by commit
>
> 5caaed151a68 ("netfilter: conntrack: don't cache nlattr_tuple_size result in nla_size")
I assume that this warning will now be in the net-next tree ...
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-11-08 8:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 0:02 linux-next: build warning after merge of the netfilter-next tree Stephen Rothwell
2017-11-08 8:00 ` Stephen Rothwell [this message]
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
-- 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
2018-01-02 1:14 Stephen Rothwell
2018-01-02 15:30 ` Pablo Neira Ayuso
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=20171108190052.63dfd8ce@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).