From: Stephen Hemminger <stephen@networkplumber.org>
To: marcel@holtmann.org, gustavo@padovan.org,
johan.hedberg@gmail.com, davem@davemloft.net,
pablo@netfilter.org, kadlec@blackhole.kfki.hu, fw@strlen.de
Cc: netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
Stephen Hemminger <sthemmin@microsoft.com>
Subject: [PATCH net-next 4/6] netfilter: remove unused variable
Date: Mon, 24 Jul 2017 10:25:21 -0700 [thread overview]
Message-ID: <20170724172523.13135-5-sthemmin@microsoft.com> (raw)
In-Reply-To: <20170724172523.13135-1-sthemmin@microsoft.com>
warning: ‘recent_old_fops’ defined but not used
Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
---
net/netfilter/xt_recent.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/netfilter/xt_recent.c b/net/netfilter/xt_recent.c
index 3f6c4fa78bdb..245fa350a7a8 100644
--- a/net/netfilter/xt_recent.c
+++ b/net/netfilter/xt_recent.c
@@ -106,7 +106,7 @@ static DEFINE_SPINLOCK(recent_lock);
static DEFINE_MUTEX(recent_mutex);
#ifdef CONFIG_PROC_FS
-static const struct file_operations recent_old_fops, recent_mt_fops;
+static const struct file_operations recent_mt_fops;
#endif
static u_int32_t hash_rnd __read_mostly;
--
2.11.0
next prev parent reply other threads:[~2017-07-24 17:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 17:25 [PATCH net-next 0/6] network related warning fixes Stephen Hemminger
2017-07-24 17:25 ` [PATCH net-next 1/6] bnxt: fix unsigned comparsion with 0 Stephen Hemminger
2017-07-24 17:48 ` Michael Chan
2017-07-24 17:25 ` [PATCH net-next 2/6] bnxt: fix unused variable warnings Stephen Hemminger
2017-07-24 17:50 ` Michael Chan
2017-07-24 17:25 ` [PATCH net-next 3/6] benet: fix set but not used warning Stephen Hemminger
2017-07-24 17:25 ` Stephen Hemminger [this message]
2017-07-24 17:25 ` [PATCH net-next 5/6] socket: fix set " Stephen Hemminger
2017-07-24 17:25 ` [PATCH net-next 6/6] 6lowpan: " Stephen Hemminger
2017-07-25 12:45 ` Luiz Augusto von Dentz
2017-07-25 19:31 ` [PATCH net-next 0/6] network related warning fixes David Miller
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=20170724172523.13135-5-sthemmin@microsoft.com \
--to=stephen@networkplumber.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=sthemmin@microsoft.com \
/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).