From: Arturo Borrero <arturo.borrero.glez@gmail.com>
To: netfilter-devel@vger.kernel.org
Cc: pablo@netfilter.org
Subject: [libnftables PATCH] data_reg: Delete trailing space in snprintf_xml
Date: Tue, 28 May 2013 17:07:02 +0200 [thread overview]
Message-ID: <20130528150702.5328.73876.stgit@nfdev.cica.es> (raw)
A minor cosmetic change. Delete the space before '>'.
Signed-off-by: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
---
src/expr/data_reg.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/expr/data_reg.c b/src/expr/data_reg.c
index 5ebc1de..11e4de8 100644
--- a/src/expr/data_reg.c
+++ b/src/expr/data_reg.c
@@ -291,7 +291,7 @@ int nft_data_reg_value_snprintf_xml(char *buf, size_t size,
uint8_t *tmp;
int data_len = reg->len/sizeof(uint32_t);
- ret = snprintf(buf, len, "<data_reg type=\"value\" >");
+ ret = snprintf(buf, len, "<data_reg type=\"value\">");
SNPRINTF_BUFFER_SIZE(ret, size, len, offset);
ret = snprintf(buf+offset, len, "<len>%d</len>", data_len);
@@ -351,7 +351,7 @@ int nft_data_reg_snprintf(char *buf, size_t size, union nft_data_reg *reg,
switch(output_format) {
case NFT_RULE_O_XML:
return snprintf(buf, size,
- "<data_reg type=\"verdict\" >"
+ "<data_reg type=\"verdict\">"
"<verdict>%d</verdict>"
"</data_reg>", reg->verdict);
case NFT_RULE_O_DEFAULT:
@@ -363,7 +363,7 @@ int nft_data_reg_snprintf(char *buf, size_t size, union nft_data_reg *reg,
switch(output_format) {
case NFT_RULE_O_XML:
return snprintf(buf, size,
- "<data_reg type=\"chain\" >"
+ "<data_reg type=\"chain\">"
"<chain>%s</chain>"
"</data_reg>", reg->chain);
case NFT_RULE_O_DEFAULT:
next reply other threads:[~2013-05-28 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 15:07 Arturo Borrero [this message]
2013-05-29 12:12 ` [libnftables PATCH] data_reg: Delete trailing space in snprintf_xml 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=20130528150702.5328.73876.stgit@nfdev.cica.es \
--to=arturo.borrero.glez@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).