From: Ana Rey <anarey@gmail.com>
To: netfilter-devel@vger.kernel.org
Cc: Ana Rey <anarey@gmail.com>
Subject: [libnftnl PATCH 0/5] expr: bitwise: Do not print unset values
Date: Thu, 19 Jun 2014 17:07:05 +0200 [thread overview]
Message-ID: <1403190430-22173-1-git-send-email-anarey@gmail.com> (raw)
This patchset does tasks about does not print unset value in xml and json file
and about refactoring code:
*"expr: byteorder: Get a nft_rule_expr type in
nft_rule_expr_byteorder_snprintf_* functions"
* "expr: byteorder: Use nft_rule_expr_set_* in the xml parsing code"
* "expr: byteorder: Rename variables in
nft_rule_expr_byteorder_json_parse functions"
*** BLURB HERE ***
Ana Rey (5):
expr: byteorder: Get a nft_rule_expr type in
nft_rule_expr_byteorder_snprintf_* functions
expr: byteorder: Use nft_rule_expr_set_* in the xml parsing code
expr: byteorder: Do not print unset values in xml file
expr: byteorder: Rename variables in
nft_rule_expr_byteorder_json_parse functions
expr: byteorder: Do not print unset values in json
src/expr/byteorder.c | 196 +++++++++++++++++++++++++++------------------------
1 file changed, 102 insertions(+), 94 deletions(-)
--
2.0.0
next 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 Ana Rey [this message]
2014-06-19 15:07 ` [libnftnl PATCH 1/5] expr: byteorder: Get a nft_rule_expr type in nft_rule_expr_byteorder_snprintf_* functions Ana Rey
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-1-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).