From: Patrick McHardy <kaber@trash.net>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCH 1/4] nftables: shorten "could not process rule in batch" message
Date: Fri, 10 Jan 2014 09:31:31 +0000 [thread overview]
Message-ID: <1389346294-7242-2-git-send-email-kaber@trash.net> (raw)
In-Reply-To: <1389346294-7242-1-git-send-email-kaber@trash.net>
Remove the "in batch" part, it makes most messages exceed a single line, the
user doesn't care about this and we process even single rules in "batches".
Signed-off-by: Patrick McHardy <kaber@trash.net>
---
src/main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/main.c b/src/main.c
index 32a991a..e8be423 100644
--- a/src/main.c
+++ b/src/main.c
@@ -183,8 +183,8 @@ static int nft_netlink(struct parser_state *state, struct list_head *msgs)
if (err->seqnum == cmd->seqnum ||
err->seqnum == batch_seqnum) {
netlink_io_error(&ctx, &cmd->location,
- "Could not process rule in batch: %s",
- strerror(err->err));
+ "Could not process rule: %s",
+ strerror(err->err));
if (err->seqnum == cmd->seqnum) {
mnl_err_list_free(err);
break;
--
1.8.4.2
next prev parent reply other threads:[~2014-01-10 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 9:31 [PATCH 0/4] nftables: bug fixes and minor cleanups Patrick McHardy
2014-01-10 9:31 ` Patrick McHardy [this message]
2014-01-10 9:31 ` [PATCH 2/4] erec: fix error markup for errors starting at column 0 Patrick McHardy
2014-01-10 9:31 ` [PATCH 3/4] datatype: revert "fix crash if wrong integer type is passed" Patrick McHardy
2014-01-10 9:31 ` [PATCH 4/4] meta: fix crash when parsing unresolvable mark values 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=1389346294-7242-2-git-send-email-kaber@trash.net \
--to=kaber@trash.net \
--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).