From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Reshetova, Elena" <elena.reshetova@intel.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
NetFilter <netfilter-devel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Hans Liljestrand" <ishkamiel@gmail.com>,
Kees Cook <keescook@chromium.org>,
David Windsor <dwindsor@gmail.com>
Subject: Re: linux-next: build warning after merge of the netfilter-next tree
Date: Mon, 20 Mar 2017 19:44:55 +1100 [thread overview]
Message-ID: <20170320194455.4352d15e@canb.auug.org.au> (raw)
In-Reply-To: <2236FBA76BA1254E88B949DDB74E612B41C5B0DC@IRSMSX102.ger.corp.intel.com>
Hi Elena,
On Mon, 20 Mar 2017 07:00:13 +0000 "Reshetova, Elena" <elena.reshetova@intel.com> wrote:
>
> > After merging the netfilter-next tree, today's linux-next build (x86_64
> > allmodconfig) produced this warning:
> >
> > net/netfilter/nfnetlink_acct.c: In function 'nfnl_acct_try_del':
> > net/netfilter/nfnetlink_acct.c:329:15: warning: unused variable 'refcount' [-
> > Wunused-variable]
> > unsigned int refcount;
> > ^
> >
> > Introduced by commit
>
> Ups, sorry about this, slipped through. Should I submit a fix or how do you want to handle this?
That's up to Pablo, but presumably you should send him a followup patch.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-03-20 8:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 0:12 linux-next: build warning after merge of the netfilter-next tree Stephen Rothwell
2017-03-20 7:00 ` Reshetova, Elena
2017-03-20 8:44 ` Stephen Rothwell [this message]
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
2018-01-02 1:14 Stephen Rothwell
2018-01-02 15:30 ` Pablo Neira Ayuso
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
2020-03-30 0:26 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=20170320194455.4352d15e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dwindsor@gmail.com \
--cc=elena.reshetova@intel.com \
--cc=ishkamiel@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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).