From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Simon Horman <horms@verge.net.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the ipvs-next tree
Date: Fri, 15 Apr 2016 11:56:07 +0200 [thread overview]
Message-ID: <20160415095607.GC1561@salvia> (raw)
In-Reply-To: <20160415105748.5b8754fc@canb.auug.org.au>
On Fri, Apr 15, 2016 at 10:57:48AM +1000, Stephen Rothwell wrote:
> Hi Simon,
>
> After merging the ipvs-next tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> net/netfilter/nf_conntrack_netlink.c:529:15: warning: 'ctnetlink_proto_size' defined but not used [-Wunused-function]
> static size_t ctnetlink_proto_size(const struct nf_conn *ct)
> ^
> net/netfilter/nf_conntrack_netlink.c:546:15: warning: 'ctnetlink_acct_size' defined but not used [-Wunused-function]
> static size_t ctnetlink_acct_size(const struct nf_conn *ct)
> ^
> net/netfilter/nf_conntrack_netlink.c:556:12: warning: 'ctnetlink_secctx_size' defined but not used [-Wunused-function]
> static int ctnetlink_secctx_size(const struct nf_conn *ct)
> ^
> net/netfilter/nf_conntrack_netlink.c:572:15: warning: 'ctnetlink_timestamp_size' defined but not used [-Wunused-function]
> static size_t ctnetlink_timestamp_size(const struct nf_conn *ct)
> ^
> Introduced by commit
>
> 4054ff45454a ("netfilter: ctnetlink: remove unnecessary inlining")
>
> This build does not set CONFIG_NF_CONNTRACK_EVENTS or
> CONFIG_NETFILTER_NETLINK_GLUE_CT.
This is my fault, will fix this asap. Thanks for reporting.
next prev parent reply other threads:[~2016-04-15 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 0:57 linux-next: build warning after merge of the ipvs-next tree Stephen Rothwell
2016-04-15 9:56 ` Pablo Neira Ayuso [this message]
2016-04-15 12:38 ` Simon Horman
2016-04-18 9:09 ` Pablo Neira Ayuso
2016-04-19 3:44 ` Simon Horman
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=20160415095607.GC1561@salvia \
--to=pablo@netfilter.org \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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).