automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw138166 [PATCH] net/bnx2x: fix indentation
Date: Mon, 11 Mar 2024 17:47:46 +0100 (CET)	[thread overview]
Message-ID: <20240311164746.C6FCA1223EF@dpdk.org> (raw)
In-Reply-To: <20240311163912.11229-1-stephen@networkplumber.org>

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

_coding style issues_


WARNING:BRACES: braces {} are not necessary for single statement blocks
#109: FILE: drivers/net/bnx2x/bnx2x_stats.c:494:
+	if (IS_VF(sc)) {
+		return;
+	}

WARNING:BRACES: braces {} are not necessary for any arm of this statement
#116: FILE: drivers/net/bnx2x/bnx2x_stats.c:498:
+	if (sc->port.pmf) {
[...]
-    else if (sc->func_stx) {
[...]

WARNING:BRACES: braces {} are not necessary for single statement blocks
#123: FILE: drivers/net/bnx2x/bnx2x_stats.c:502:
+	else if (sc->func_stx) {
+		bnx2x_func_stats_init(sc);
+	}

CHECK:CAMELCASE: Avoid CamelCase: <funcID>
#223: FILE: drivers/net/bnx2x/bnx2x_stats.c:1376:
+	cur_query_entry->funcID = htole16(SC_FUNC(sc));

total: 0 errors, 3 warnings, 1 checks, 230 lines checked

  parent reply	other threads:[~2024-03-11 16:47 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240311163912.11229-1-stephen@networkplumber.org>
2024-03-11 16:23 ` |SUCCESS| " qemudev
2024-03-11 16:27 ` qemudev
2024-03-11 16:47 ` checkpatch [this message]
2024-03-11 17:32 ` dpdklab
2024-03-11 17:33 ` dpdklab
2024-03-11 17:33 ` dpdklab
2024-03-11 17:33 ` dpdklab
2024-03-11 17:34 ` dpdklab
2024-03-11 17:34 ` dpdklab
2024-03-11 17:38 ` dpdklab
2024-03-11 17:38 ` dpdklab
2024-03-11 17:39 ` dpdklab
2024-03-11 17:39 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:40 ` dpdklab
2024-03-11 17:41 ` dpdklab
2024-03-11 17:41 ` dpdklab
2024-03-11 17:41 ` dpdklab
2024-03-11 17:42 ` dpdklab
2024-03-11 17:42 ` dpdklab
2024-03-11 17:42 ` dpdklab
2024-03-11 17:42 ` dpdklab
2024-03-11 17:42 ` 0-day Robot
2024-03-11 17:43 ` dpdklab
2024-03-11 17:43 ` dpdklab
2024-03-11 17:45 ` dpdklab
2024-03-11 17:45 ` dpdklab
2024-03-11 17:46 ` dpdklab
2024-03-11 17:46 ` dpdklab
2024-03-11 17:46 ` dpdklab
2024-03-11 17:46 ` dpdklab
2024-03-11 17:46 ` dpdklab
2024-03-11 17:46 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:47 ` dpdklab
2024-03-11 17:48 ` dpdklab
2024-03-11 17:48 ` dpdklab
2024-03-11 17:48 ` dpdklab
2024-03-11 17:49 ` dpdklab
2024-03-11 17:49 ` dpdklab
2024-03-11 17:49 ` dpdklab
2024-03-11 17:49 ` dpdklab
2024-03-11 17:50 ` dpdklab
2024-03-11 17:53 ` dpdklab
2024-03-11 17:54 ` dpdklab
2024-03-11 17:55 ` dpdklab
2024-03-11 18:35 ` dpdklab
2024-03-11 18:40 ` dpdklab
2024-03-11 18:44 ` dpdklab
2024-03-11 18:49 ` dpdklab
2024-03-11 18:55 ` dpdklab
2024-03-11 23:00 ` dpdklab
2024-03-11 23:04 ` dpdklab
2024-03-11 23:08 ` dpdklab
2024-03-11 23:14 ` dpdklab
2024-03-15  1:59 ` dpdklab
2024-03-15  2:25 ` 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=20240311164746.C6FCA1223EF@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=stephen@networkplumber.org \
    --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).