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| pw139010 [PATCH v20 14/14] log: colorize log output
Date: Sat, 30 Mar 2024 17:47:19 +0100 (CET)	[thread overview]
Message-ID: <20240330164719.20ECF1223FC@dpdk.org> (raw)
In-Reply-To: <20240330164433.50144-15-stephen@networkplumber.org>

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

_coding style issues_


WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 8)
#266: FILE: lib/log/log.c:522:
 	else
[...]
+	if (log_color_enabled(is_terminal)) {

WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#298: FILE: lib/log/log_color.c:5:
+#include <stdio.h>

ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#348: FILE: lib/log/log_color.c:55:
+static int color_fprintf(FILE *out, enum color color, const char *fmt, ...)
                               ^

total: 1 errors, 2 warnings, 336 lines checked

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

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240330164433.50144-15-stephen@networkplumber.org>
2024-03-30 16:24 ` |SUCCESS| pw138997-139010 " qemudev
2024-03-30 16:28 ` qemudev
2024-03-30 16:47 ` checkpatch [this message]
2024-03-30 17:28 ` |SUCCESS| pw138997-139010 [PATCH] [v20,14/14] log: colorize log outp dpdklab
2024-03-30 17:28 ` dpdklab
2024-03-30 17:29 ` dpdklab
2024-03-30 17:30 ` dpdklab
2024-03-30 17:31 ` dpdklab
2024-03-30 17:32 ` dpdklab
2024-03-30 17:33 ` dpdklab
2024-03-30 17:34 ` dpdklab
2024-03-30 17:34 ` dpdklab
2024-03-30 17:34 ` dpdklab
2024-03-30 17:35 ` dpdklab
2024-03-30 17:35 ` dpdklab
2024-03-30 17:35 ` dpdklab
2024-03-30 17:36 ` dpdklab
2024-03-30 17:36 ` dpdklab
2024-03-30 17:36 ` dpdklab
2024-03-30 17:36 ` dpdklab
2024-03-30 17:37 ` dpdklab
2024-03-30 17:37 ` dpdklab
2024-03-30 17:38 ` dpdklab
2024-03-30 17:39 ` dpdklab
2024-03-30 17:40 ` dpdklab
2024-03-30 17:40 ` dpdklab
2024-03-30 17:40 ` dpdklab
2024-03-30 17:41 ` dpdklab
2024-03-30 17:41 ` dpdklab
2024-03-30 17:42 ` dpdklab
2024-03-30 17:42 ` dpdklab
2024-03-30 17:43 ` dpdklab
2024-03-30 17:43 ` dpdklab
2024-03-30 17:44 ` dpdklab
2024-03-30 17:44 ` dpdklab
2024-03-30 17:45 ` dpdklab
2024-03-30 17:45 ` dpdklab
2024-03-30 17:45 ` |SUCCESS| pw139010 [PATCH v20 14/14] log: colorize log output 0-day Robot
2024-03-30 17:47 ` |SUCCESS| pw138997-139010 [PATCH] [v20,14/14] log: colorize log outp dpdklab
2024-03-30 17:47 ` dpdklab
2024-03-30 17:47 ` dpdklab
2024-03-30 17:48 ` dpdklab
2024-03-30 17:48 ` dpdklab
2024-03-30 17:49 ` dpdklab
2024-03-30 17:49 ` dpdklab
2024-03-30 17:49 ` dpdklab
2024-03-30 17:50 ` dpdklab
2024-03-30 17:50 ` dpdklab
2024-03-30 17:50 ` dpdklab
2024-03-30 17:50 ` dpdklab
2024-03-30 17:50 ` dpdklab
2024-03-30 17:50 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:52 ` dpdklab
2024-03-30 17:52 ` dpdklab
2024-03-30 17:52 ` dpdklab
2024-03-30 17:52 ` dpdklab
2024-03-30 17:52 ` dpdklab
2024-03-30 17:52 ` dpdklab
2024-03-30 17:52 ` dpdklab
2024-03-30 17:53 ` dpdklab
2024-03-30 17:54 ` dpdklab
2024-03-30 17:54 ` dpdklab
2024-03-30 17:55 ` dpdklab
2024-03-30 17:55 ` dpdklab
2024-03-30 17:58 ` dpdklab
2024-03-30 18:00 ` dpdklab
2024-03-30 18:02 ` dpdklab
2024-03-30 18:02 ` dpdklab
2024-03-30 18:03 ` dpdklab
2024-03-30 18:04 ` dpdklab
2024-03-30 18:05 ` dpdklab
2024-03-30 18:06 ` dpdklab
2024-03-30 18:13 ` dpdklab
2024-03-30 18:14 ` dpdklab
2024-03-30 18:15 ` dpdklab
2024-03-30 18:42 ` dpdklab
2024-03-30 18:59 ` dpdklab
2024-03-30 19:10 ` dpdklab
2024-04-03  2:50 ` dpdklab
2024-04-03  2:59 ` dpdklab
2024-04-03  3:14 ` dpdklab
2024-04-03  3:24 ` dpdklab
2024-04-03  3:48 ` 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=20240330164719.20ECF1223FC@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).