From: kbuild test robot <lkp@intel.com>
To: Florian Westphal <fw@strlen.de>
Cc: kbuild-all@01.org, netfilter-devel@vger.kernel.org,
Florian Westphal <fw@strlen.de>
Subject: [RFC PATCH] netfilter: meta: nft_meta_get_validate() can be static
Date: Wed, 13 Dec 2017 15:16:22 +0800 [thread overview]
Message-ID: <20171213071622.GA138460@ivb43.lkp.intel.com> (raw)
In-Reply-To: <20171201124021.20973-2-fw@strlen.de>
Fixes: dce1fc524886 ("netfilter: meta: secpath support")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
nft_meta.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/net/netfilter/nft_meta.c b/net/netfilter/nft_meta.c
index 63a013a..993157e 100644
--- a/net/netfilter/nft_meta.c
+++ b/net/netfilter/nft_meta.c
@@ -328,9 +328,9 @@ int nft_meta_get_init(const struct nft_ctx *ctx,
}
EXPORT_SYMBOL_GPL(nft_meta_get_init);
-int nft_meta_get_validate(const struct nft_ctx *ctx,
- const struct nft_expr *expr,
- const struct nft_data **data)
+static int nft_meta_get_validate(const struct nft_ctx *ctx,
+ const struct nft_expr *expr,
+ const struct nft_data **data)
{
const struct nft_meta *priv = nft_expr_priv(expr);
unsigned int hooks;
next prev parent reply other threads:[~2017-12-13 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 12:40 [PATCH next] nftables: add inbound ipsec matching Florian Westphal
2017-12-01 12:40 ` [PATCH nf-next] netfilter: meta: secpath support Florian Westphal
2017-12-01 12:40 ` Florian Westphal
2017-12-01 12:53 ` Arturo Borrero Gonzalez
2017-12-01 13:07 ` Florian Westphal
2017-12-13 7:16 ` kbuild test robot [this message]
2017-12-13 16:42 ` [RFC PATCH] netfilter: meta: nft_meta_get_validate() can be static Pablo Neira Ayuso
2017-12-13 7:16 ` [PATCH nf-next] netfilter: meta: secpath support kbuild test robot
2017-12-01 12:40 ` [PATCH libnftnl] " Florian Westphal
2017-12-01 12:40 ` [PATCH nft] meta: add " Florian Westphal
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=20171213071622.GA138460@ivb43.lkp.intel.com \
--to=lkp@intel.com \
--cc=fw@strlen.de \
--cc=kbuild-all@01.org \
--cc=netfilter-devel@vger.kernel.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).