From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: kaber@trash.net, admin@rollinix.net, niels@kristensen.io, tom@compton.nu
Subject: [PATCH nft 1/3] rule: use netlink_add_setelems() when creating literal sets
Date: Fri, 19 Jun 2015 15:15:16 +0200 [thread overview]
Message-ID: <1434719718-10371-1-git-send-email-pablo@netfilter.org> (raw)
Thus, do_add_setelems() is only used for set declarations.
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
---
src/rule.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/rule.c b/src/rule.c
index b2090dd..a4c685c 100644
--- a/src/rule.c
+++ b/src/rule.c
@@ -706,7 +706,7 @@ static int do_add_set(struct netlink_ctx *ctx, const struct handle *h,
if (set->flags & SET_F_INTERVAL &&
set_to_intervals(ctx->msgs, set) < 0)
return -1;
- if (do_add_setelems(ctx, &set->handle, set->init) < 0)
+ if (netlink_add_setelems(ctx, &set->handle, set->init) < 0)
return -1;
}
return 0;
--
1.7.10.4
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
next reply other threads:[~2015-06-19 13:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 13:15 Pablo Neira Ayuso [this message]
2015-06-19 13:15 ` [PATCH nft 2/3] segtree: pass element expression as parameter to set_to_intervals() Pablo Neira Ayuso
2015-06-19 13:15 ` [PATCH nft 3/3] rule: fix use of intervals in set declarations Pablo Neira Ayuso
2015-06-19 13:13 ` Patrick McHardy
2015-06-19 13:48 ` Pablo Neira Ayuso
2015-06-19 13:44 ` Patrick McHardy
2015-06-19 13:59 ` Pablo Neira Ayuso
2015-06-19 13:59 ` Patrick McHardy
2015-06-19 17:40 ` Pablo Neira Ayuso
2015-06-19 18:01 ` Patrick McHardy
2015-06-19 18:15 ` Patrick McHardy
2015-06-20 11:06 ` Pablo Neira Ayuso
2015-06-20 11:41 ` Patrick McHardy
2015-06-20 18:37 ` 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=1434719718-10371-1-git-send-email-pablo@netfilter.org \
--to=pablo@netfilter.org \
--cc=admin@rollinix.net \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=niels@kristensen.io \
--cc=tom@compton.nu \
/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).