netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: kbuild-all@01.org, netfilter-devel@vger.kernel.org,
	coreteam@netfilter.org
Subject: [RFC PATCH nf-next] netfilter: core: __nf_unregister_net_hook() can be static
Date: Wed, 20 Dec 2017 01:25:40 +0800	[thread overview]
Message-ID: <20171219172540.GA56682@lkp-sb05> (raw)
In-Reply-To: <201712200120.UwkYYVXx%fengguang.wu@intel.com>


Fixes: ac119d8cd089 ("netfilter: core: support for NFPROTO_INET hook registration")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
 core.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/net/netfilter/core.c b/net/netfilter/core.c
index 606efc9..9ace162 100644
--- a/net/netfilter/core.c
+++ b/net/netfilter/core.c
@@ -400,8 +400,8 @@ static void nf_remove_net_hook(struct nf_hook_entries *old,
 	}
 }
 
-void __nf_unregister_net_hook(struct net *net, int pf,
-			      const struct nf_hook_ops *reg)
+static void __nf_unregister_net_hook(struct net *net, int pf,
+				     const struct nf_hook_ops *reg)
 {
 	struct nf_hook_entries __rcu **pp;
 	struct nf_hook_entries *p;

  reply	other threads:[~2017-12-19 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 17:25 [nf-next:for-net-next3 28/40] net/netfilter/core.c:403:6: sparse: symbol '__nf_unregister_net_hook' was not declared. Should it be static? kbuild test robot
2017-12-19 17:25 ` kbuild test robot [this message]
2017-12-20 23:18   ` [RFC PATCH nf-next] netfilter: core: __nf_unregister_net_hook() can be static Pablo Neira Ayuso

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=20171219172540.GA56682@lkp-sb05 \
    --to=fengguang.wu@intel.com \
    --cc=coreteam@netfilter.org \
    --cc=kbuild-all@01.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).