From: Ana Rey <anarey@gmail.com>
To: netfilter-devel@vger.kernel.org
Cc: Ana Rey <anarey@gmail.com>
Subject: [libnftnl PATCH v4 0/3] Do not print unset value in xml file
Date: Tue, 3 Jun 2014 12:41:53 +0200 [thread overview]
Message-ID: <1401792116-17742-1-git-send-email-anarey@gmail.com> (raw)
Hi,
In this version, I add a new patch:
"expr: log: Rename variables in nft_rule_expr_log_json_parse functions"
It removes these changes out of "Use nft_rule_expr_set_* in the xml parsing code"
patch.
Also, I fix some errors with nft_rule_expr_set_* functions in
"Use nft_rule_expr_set_* in the xml parsing code" patch.
[Change in v3:]
In this version, I rename some variables, I fix writing errors in the patch
description and I fix wrong indentation.
[Change in v2:]
Hi,
After some advises of Arturo Borrero, I send a previous patch to
'Code refactoring to use nft_rule_expr_set_* functions' patch and v2 of
"Do not print unset values in xml" patch.
Ana Rey (3):
expr: log: Rename variables in nft_rule_expr_log_json_parse functions
expr: log: Use nft_rule_expr_set_* in the xml parsing code
expr: log: Do not print unset values in xml
src/expr/log.c | 95 +++++++++++++++++++++++++++++++++-------------------------
1 file changed, 54 insertions(+), 41 deletions(-)
--
2.0.0.rc2
next reply other threads:[~2014-06-03 10:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 10:41 Ana Rey [this message]
2014-06-03 10:41 ` [libnftnl PATCH v4 1/3] expr: log: Rename variables in nft_rule_expr_log_json_parse functions Ana Rey
2014-06-05 13:17 ` Pablo Neira Ayuso
2014-06-03 10:41 ` [libnftnl PATCH v4 2/3] expr: log: Use nft_rule_expr_set_* in the xml parsing code Ana Rey
2014-06-05 13:17 ` Pablo Neira Ayuso
2014-06-03 10:41 ` [libnftnl PATCH v4 3/3] expr: log: Do not print unset values in xml Ana Rey
2014-06-05 13:18 ` 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=1401792116-17742-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).