automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: |WARNING| pw153744 [PATCH 3/3] argparse: use enums to remove max-value defines in lists
Date: Tue, 27 May 2025 11:22:10 +0200 (CEST)	[thread overview]
Message-ID: <20250527092210.C1306125267@dpdk.org> (raw)
In-Reply-To: <20250527092113.903910-4-bruce.richardson@intel.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153744

_coding style issues_


WARNING:LONG_LINE: line length of 129 exceeds 100 columns
#107: FILE: app/test/test_argparse.c:82:
+		{ "--abc", "-a", "abc argument", (void *)1, (void *)1, RTE_ARGPARSE_VALUE_NONE, RTE_ARGPARSE_VALUE_TYPE_NONE }, \

WARNING:LONG_LINE: line length of 129 exceeds 100 columns
#108: FILE: app/test/test_argparse.c:83:
+		{ "--xyz", "-x", "xyz argument", (void *)1, (void *)2, RTE_ARGPARSE_VALUE_NONE, RTE_ARGPARSE_VALUE_TYPE_NONE }, \

WARNING:LONG_LINE: line length of 101 exceeds 100 columns
#606: FILE: app/test/test_argparse.c:845:
+	ret = rte_argparse_parse_type(bool_numeric_invalid, RTE_ARGPARSE_VALUE_TYPE_BOOL, &val_bool);

ERROR:SWITCH_CASE_INDENT_LEVEL: switch and case should be at the same indent
#753: FILE: lib/argparse/rte_argparse.c:36:
+	switch (arg->value_required) {
+		case RTE_ARGPARSE_VALUE_NONE:
+		case RTE_ARGPARSE_VALUE_OPTIONAL:
+		case RTE_ARGPARSE_VALUE_REQUIRED:

ERROR:SWITCH_CASE_INDENT_LEVEL: switch and case should be at the same indent
#770: FILE: lib/argparse/rte_argparse.c:49:
+	switch (arg->value_type) {
+		case RTE_ARGPARSE_VALUE_TYPE_NONE:
+		case RTE_ARGPARSE_VALUE_TYPE_INT:
+		case RTE_ARGPARSE_VALUE_TYPE_U8:
+		case RTE_ARGPARSE_VALUE_TYPE_U16:
+		case RTE_ARGPARSE_VALUE_TYPE_U32:
+		case RTE_ARGPARSE_VALUE_TYPE_U64:
+		case RTE_ARGPARSE_VALUE_TYPE_STR:
+		case RTE_ARGPARSE_VALUE_TYPE_BOOL:

WARNING:LONG_LINE: line length of 103 exceeds 100 columns
#965: FILE: lib/argparse/rte_argparse.c:670:
+					ARGPARSE_LOG(ERR, "argument %s doesn't have value!", arg_name);

total: 2 errors, 4 warnings, 954 lines checked

  parent reply	other threads:[~2025-05-27  9:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250527092113.903910-4-bruce.richardson@intel.com>
2025-05-27  8:47 ` |SUCCESS| pw153742-153744 " qemudev
2025-05-27  8:52 ` qemudev
2025-05-27  9:22 ` checkpatch [this message]
2025-05-27 10:25 ` |SUCCESS| pw153744 " 0-day Robot
2025-05-27 10:30 ` |SUCCESS| pw153742-153744 [PATCH] [3/3] argparse: use enums to remov dpdklab
2025-05-27 10:37 ` dpdklab
2025-05-27 10:39 ` dpdklab
2025-05-27 10:54 ` dpdklab
2025-05-27 11:07 ` |PENDING| " dpdklab
2025-05-27 11:08 ` |SUCCESS| " dpdklab
2025-05-27 11:35 ` |PENDING| " dpdklab
2025-05-27 11:35 ` dpdklab
2025-05-27 12:38 ` |SUCCESS| " dpdklab
2025-05-27 12:47 ` dpdklab
2025-05-27 13:04 ` dpdklab
2025-05-27 13:10 ` |WARNING| " dpdklab
2025-05-27 13:42 ` |SUCCESS| " dpdklab
2025-05-27 14:38 ` dpdklab
2025-05-27 16:53 ` dpdklab
2025-06-03 19:58 ` dpdklab
2025-06-04  1:44 ` dpdklab

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=20250527092210.C1306125267@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=bruce.richardson@intel.com \
    --cc=test-report@dpdk.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).