[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <121171795.jNF1vkL58j@wuerfel>
Date: Thu, 28 Jan 2016 13:28:17 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Simon Horman <horms@...ge.net.au>
Cc: Julian Anastasov <ja@....bg>, Wensong Zhang <wensong@...ux-vs.org>,
linux-arm-kernel@...ts.infradead.org,
Pablo Neira Ayuso <pablo@...filter.org>,
Patrick McHardy <kaber@...sh.net>,
Jozsef Kadlecsik <kadlec@...ckhole.kfki.hu>,
"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
lvs-devel@...r.kernel.org, netfilter-devel@...r.kernel.org,
coreteam@...filter.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] netfilter: ipvs: avoid unused variable warnings
On Thursday 28 January 2016 08:39:53 Simon Horman wrote:
> On Wed, Jan 27, 2016 at 10:01:42PM +0200, Julian Anastasov wrote:
> >
> > Hello,
> >
> > On Wed, 27 Jan 2016, Arnd Bergmann wrote:
> >
> > > The proc_create() and remove_proc_entry() functions do not reference
> > > their arguments when CONFIG_PROC_FS is disabled, so we get a couple
> > > of warnings about unused variables in IPVS:
> > >
> > > ipvs/ip_vs_app.c:608:14: warning: unused variable 'net' [-Wunused-variable]
> > > ipvs/ip_vs_ctl.c:3950:14: warning: unused variable 'net' [-Wunused-variable]
> > > ipvs/ip_vs_ctl.c:3994:14: warning: unused variable 'net' [-Wunused-variable]
> > >
> > > This removes the local variables and instead looks them up separately
> > > for each use, which obviously avoids the warning.
> > >
> > > Signed-off-by: Arnd Bergmann <arnd@...db.de>
> > > Fixes: 4c50a8ce2b63 ("netfilter: ipvs: avoid unused variable warning")
> >
> > Looks like your previous patch for ip_vs_app_net_cleanup
> > was delayed in ipvs-next tree. I guess, Simon should drop it and
> > use this one instead when net-next opens:
> >
> > Acked-by: Julian Anastasov <ja@....bg>
>
> Thanks, and sorry about not pushing the other patch to net-next.
> I have dropped it and queued up this one in its place.
Ah, I had not realized that the other patch was still in ipvs-next
and not merged in mainline. I did most of my testing on linux-next
(with the previous patch) and then validated the new one on
4.5-rc1, which led me to update it to contain the same hunk again.
Replacing the original patch works fine though, thanks for picking
it up!
Arnd
Powered by blists - more mailing lists