[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160419034412.GA8968@verge.net.au>
Date: Tue, 19 Apr 2016 13:44:16 +1000
From: Simon Horman <horms@...ge.net.au>
To: Pablo Neira Ayuso <pablo@...filter.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build warning after merge of the ipvs-next tree
On Mon, Apr 18, 2016 at 11:09:21AM +0200, Pablo Neira Ayuso wrote:
> On Fri, Apr 15, 2016 at 10:38:14PM +1000, Simon Horman wrote:
> > On Fri, Apr 15, 2016 at 11:56:07AM +0200, Pablo Neira Ayuso wrote:
> > > 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.
> >
> > Pablo,
> >
> > can you let me know when it is fixed in nf-next so I can rebase ipvs-next
> > accordingly?
>
> No need to rebase, will push an incremental fix for this.
Thanks, understood.
Powered by blists - more mailing lists