From: Giuseppe Longo <giuseppelng@gmail.com>
To: netfilter-devel@vger.kernel.org
Cc: Giuseppe Longo <giuseppelng@gmail.com>
Subject: [PATCH 2/3] nft-shared: make compare_matches as public
Date: Wed, 1 Oct 2014 16:47:09 +0200 [thread overview]
Message-ID: <1412174830-3620-2-git-send-email-giuseppelng@gmail.com> (raw)
In-Reply-To: <1412174830-3620-1-git-send-email-giuseppelng@gmail.com>
This permits to compare two xtables_ebt_entry's matches reusing compare_matches.
Signed-off-by: Giuseppe Longo <giuseppelng@gmail.com>
---
iptables/nft-shared.c | 4 ++--
iptables/nft-shared.h | 1 +
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/iptables/nft-shared.c b/iptables/nft-shared.c
index 03f15b4..db1424f 100644
--- a/iptables/nft-shared.c
+++ b/iptables/nft-shared.c
@@ -720,8 +720,8 @@ struct nft_family_ops *nft_family_ops_lookup(int family)
return NULL;
}
-static bool
-compare_matches(struct xtables_rule_match *mt1, struct xtables_rule_match *mt2)
+bool compare_matches(struct xtables_rule_match *mt1,
+ struct xtables_rule_match *mt2)
{
struct xtables_rule_match *mp1;
struct xtables_rule_match *mp2;
diff --git a/iptables/nft-shared.h b/iptables/nft-shared.h
index ecb486c..789aaeb 100644
--- a/iptables/nft-shared.h
+++ b/iptables/nft-shared.h
@@ -134,6 +134,7 @@ struct nft_handle;
bool nft_ipv46_rule_find(struct nft_family_ops *ops, struct nft_rule *r,
struct iptables_command_state *cs);
+bool compare_matches(struct xtables_rule_match *mt1, struct xtables_rule_match *mt2);
bool compare_targets(struct xtables_target *tg1, struct xtables_target *tg2);
struct addr_mask {
--
1.8.3.2
next prev parent reply other threads:[~2014-10-01 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 14:47 [PATCH 1/3] xtables: bootstrap xtables-eb for nftables Giuseppe Longo
2014-10-01 14:47 ` Giuseppe Longo [this message]
2014-10-01 14:47 ` [PATCH 3/3] Operations for bridge family Giuseppe Longo
2014-10-01 19:20 ` [PATCH 1/3] xtables: bootstrap xtables-eb for nftables 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=1412174830-3620-2-git-send-email-giuseppelng@gmail.com \
--to=giuseppelng@gmail.com \
--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).