netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Sowden <jeremy@azazel.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>, Florian Westphal <fw@strlen.de>
Cc: Netfilter Devel <netfilter-devel@vger.kernel.org>
Subject: [PATCH libnftnl 1/3] tests: bitwise: fix error message.
Date: Mon, 24 Feb 2020 13:11:59 +0000	[thread overview]
Message-ID: <20200224131201.512755-2-jeremy@azazel.net> (raw)
In-Reply-To: <20200224131201.512755-1-jeremy@azazel.net>

In one case, the boolean test was reporting the wrong mismatched
attribute.

Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
---
 tests/nft-expr_bitwise-test.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/nft-expr_bitwise-test.c b/tests/nft-expr_bitwise-test.c
index 74a0e2aa6933..f134728fdd86 100644
--- a/tests/nft-expr_bitwise-test.c
+++ b/tests/nft-expr_bitwise-test.c
@@ -44,7 +44,7 @@ static void cmp_nftnl_expr_bool(struct nftnl_expr *rule_a,
 		print_err("bool", "Expr BITWISE_OP mismatches");
 	if (nftnl_expr_get_u16(rule_a, NFTNL_EXPR_BITWISE_LEN) !=
 	    nftnl_expr_get_u16(rule_b, NFTNL_EXPR_BITWISE_LEN))
-		print_err("bool", "Expr BITWISE_DREG mismatches");
+		print_err("bool", "Expr BITWISE_LEN mismatches");
 	nftnl_expr_get(rule_a, NFTNL_EXPR_BITWISE_MASK, &maska);
 	nftnl_expr_get(rule_b, NFTNL_EXPR_BITWISE_MASK, &maskb);
 	if (maska != maskb)
-- 
2.25.0


  reply	other threads:[~2020-02-24 13:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24 13:11 [PATCH libnftnl 0/3] bitwise: support for passing mask and xor via registers Jeremy Sowden
2020-02-24 13:11 ` Jeremy Sowden [this message]
2020-02-24 13:12 ` [PATCH libnftnl 2/3] include: update nf_tables.h Jeremy Sowden
2020-02-24 13:12 ` [PATCH libnftnl 3/3] bitwise: add support for passing mask and xor via registers Jeremy Sowden
2020-03-02 13:33 ` [PATCH libnftnl 0/3] bitwise: " 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=20200224131201.512755-2-jeremy@azazel.net \
    --to=jeremy@azazel.net \
    --cc=fw@strlen.de \
    --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).