From: Ana Rey <anarey@gmail.com>
To: netfilter-devel@vger.kernel.org
Cc: Ana Rey <anarey@gmail.com>
Subject: [nft PATCH] expression: Fix inconsistent output in set
Date: Fri, 11 Apr 2014 10:26:46 +0200 [thread overview]
Message-ID: <1daccfe0798bd032f1770b0ae7888a88db46f3f6.1397204678.git.anarey@gmail.com> (raw)
Add a whitespace between the last element in a set and the close braces.
Old output set:
set set-test {
type ipv4_address
elements = { 192.168.1.44, 192.168.2.4}
}
New output set:
set set-test {
type ipv4_address
elements = { 192.168.1.44, 192.168.2.4 }
}
Signed-off-by: Ana Rey <anarey@gmail.com>
---
src/expression.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/expression.c b/src/expression.c
index fa14d99..3b299ff 100644
--- a/src/expression.c
+++ b/src/expression.c
@@ -734,7 +734,7 @@ static void set_expr_print(const struct expr *expr)
{
printf("{ ");
compound_expr_print(expr, ", ");
- printf("}");
+ printf(" }");
}
static void set_expr_set_type(const struct expr *expr,
--
1.9.0
next reply other threads:[~2014-04-11 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 8:26 Ana Rey [this message]
2014-04-12 9:49 ` [nft PATCH] expression: Fix inconsistent output in set Patrick McHardy
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=1daccfe0798bd032f1770b0ae7888a88db46f3f6.1397204678.git.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).