From: Ana Rey <anarey@gmail.com>
To: netfilter-devel@vger.kernel.org
Cc: Ana Rey <anarey@gmail.com>
Subject: [libnftnl PATCH 1/5] expr: byteorder: Get a nft_rule_expr type in nft_rule_expr_byteorder_snprintf_* functions
Date: Thu, 19 Jun 2014 17:07:06 +0200 [thread overview]
Message-ID: <1403190430-22173-2-git-send-email-anarey@gmail.com> (raw)
In-Reply-To: <1403190430-22173-1-git-send-email-anarey@gmail.com>
Code refactoring in nft_rule_expr_byteorder_snprintf_* functions to get a
nft_rule_expr type instead of nft_expr_byorder type.
Signed-off-by: Ana Rey <anarey@gmail.com>
---
src/expr/byteorder.c | 31 +++++++++++++------------------
1 file changed, 13 insertions(+), 18 deletions(-)
diff --git a/src/expr/byteorder.c b/src/expr/byteorder.c
index 4889e80..e42d7b6 100644
--- a/src/expr/byteorder.c
+++ b/src/expr/byteorder.c
@@ -296,10 +296,10 @@ nft_rule_expr_byteorder_xml_parse(struct nft_rule_expr *e, mxml_node_t *tree,
#endif
}
-static int
-nft_rule_expr_byteorder_snprintf_json(char *buf, size_t size,
- struct nft_expr_byteorder *byteorder)
+static int nft_rule_expr_byteorder_snprintf_json(char *buf, size_t size,
+ struct nft_rule_expr *e)
{
+ struct nft_expr_byteorder *byteorder = nft_expr_data(e);
int len = size, offset = 0, ret;
ret = snprintf(buf, len, "\"sreg\":%u,"
@@ -315,10 +315,10 @@ nft_rule_expr_byteorder_snprintf_json(char *buf, size_t size,
return offset;
}
-static int
-nft_rule_expr_byteorder_snprintf_xml(char *buf, size_t size,
- struct nft_expr_byteorder *byteorder)
+static int nft_rule_expr_byteorder_snprintf_xml(char *buf, size_t size,
+ struct nft_rule_expr *e)
{
+ struct nft_expr_byteorder *byteorder = nft_expr_data(e);
int len = size, offset = 0, ret;
ret = snprintf(buf, len, "<sreg>%u</sreg>"
@@ -334,10 +334,10 @@ nft_rule_expr_byteorder_snprintf_xml(char *buf, size_t size,
return offset;
}
-static int
-nft_rule_expr_byteorder_snprintf_default(char *buf, size_t size,
- struct nft_expr_byteorder *byteorder)
+static int nft_rule_expr_byteorder_snprintf_default(char *buf, size_t size,
+ struct nft_rule_expr *e)
{
+ struct nft_expr_byteorder *byteorder = nft_expr_data(e);
int len = size, offset = 0, ret;
ret = snprintf(buf, len, "reg %u = %s(reg %u, %u, %u) ",
@@ -350,20 +350,15 @@ nft_rule_expr_byteorder_snprintf_default(char *buf, size_t size,
static int
nft_rule_expr_byteorder_snprintf(char *buf, size_t size, uint32_t type,
- uint32_t flags, struct nft_rule_expr *e)
+ uint32_t flags, struct nft_rule_expr *e)
{
- struct nft_expr_byteorder *byteorder = nft_expr_data(e);
-
switch(type) {
case NFT_OUTPUT_DEFAULT:
- return nft_rule_expr_byteorder_snprintf_default(buf, size,
- byteorder);
+ return nft_rule_expr_byteorder_snprintf_default(buf, size, e);
case NFT_OUTPUT_XML:
- return nft_rule_expr_byteorder_snprintf_xml(buf, size,
- byteorder);
+ return nft_rule_expr_byteorder_snprintf_xml(buf, size, e);
case NFT_OUTPUT_JSON:
- return nft_rule_expr_byteorder_snprintf_json(buf, size,
- byteorder);
+ return nft_rule_expr_byteorder_snprintf_json(buf, size, e);
default:
break;
}
--
2.0.0
next prev parent reply other threads:[~2014-06-19 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 15:07 [libnftnl PATCH 0/5] expr: bitwise: Do not print unset values Ana Rey
2014-06-19 15:07 ` Ana Rey [this message]
2014-06-19 15:07 ` [libnftnl PATCH 2/5] expr: byteorder: Use nft_rule_expr_set_* in the xml parsing code Ana Rey
2014-06-19 15:07 ` [libnftnl PATCH 3/5] expr: byteorder: Do not print unset values in xml file Ana Rey
2014-06-20 7:12 ` Arturo Borrero Gonzalez
2014-06-19 15:07 ` [libnftnl PATCH 4/5] expr: byteorder: Rename variables in nft_rule_expr_byteorder_json_parse functions Ana Rey
2014-06-19 15:07 ` [libnftnl PATCH 5/5] expr: byteorder: Do not print unset values in json Ana Rey
2014-06-20 7:16 ` [libnftnl PATCH 0/5] expr: bitwise: Do not print unset values Arturo Borrero Gonzalez
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=1403190430-22173-2-git-send-email-anarey@gmail.com \
--to=anarey@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).