From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw138995 [PATCH v19 15/15] log: colorize log output
Date: Sat, 30 Mar 2024 04:08:00 +0100 (CET) [thread overview]
Message-ID: <20240330030800.316401223FC@dpdk.org> (raw)
In-Reply-To: <20240330030429.4630-16-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/138995
_coding style issues_
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 8)
#267: FILE: lib/log/log.c:529:
else
[...]
+ if (log_color_enabled(is_terminal)) {
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#298: FILE: lib/log/log_color.c:4:
+#include <stdio.h>
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#348: FILE: lib/log/log_color.c:54:
+static int color_fprintf(FILE *out, enum color color, const char *fmt, ...)
^
total: 1 errors, 2 warnings, 353 lines checked
next prev parent reply other threads:[~2024-03-30 3:08 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240330030429.4630-16-stephen@networkplumber.org>
2024-03-30 2:45 ` |SUCCESS| pw138981-138995 " qemudev
2024-03-30 2:49 ` qemudev
2024-03-30 3:08 ` checkpatch [this message]
2024-03-30 3:42 ` |FAILURE| pw138981-138995 [PATCH] [v19,15/15] log: colorize log outp dpdklab
2024-03-30 3:43 ` |SUCCESS| " dpdklab
2024-03-30 3:43 ` |FAILURE| " dpdklab
2024-03-30 3:43 ` dpdklab
2024-03-30 3:44 ` |SUCCESS| " dpdklab
2024-03-30 3:44 ` dpdklab
2024-03-30 3:44 ` |FAILURE| " dpdklab
2024-03-30 3:44 ` |SUCCESS| " dpdklab
2024-03-30 3:45 ` dpdklab
2024-03-30 3:45 ` dpdklab
2024-03-30 3:45 ` dpdklab
2024-03-30 3:45 ` dpdklab
2024-03-30 3:46 ` dpdklab
2024-03-30 3:46 ` dpdklab
2024-03-30 3:47 ` dpdklab
2024-03-30 3:48 ` dpdklab
2024-03-30 3:48 ` |FAILURE| " dpdklab
2024-03-30 3:48 ` |SUCCESS| " dpdklab
2024-03-30 3:49 ` dpdklab
2024-03-30 3:50 ` dpdklab
2024-03-30 3:50 ` dpdklab
2024-03-30 3:52 ` dpdklab
2024-03-30 3:53 ` dpdklab
2024-03-30 3:54 ` dpdklab
2024-03-30 3:56 ` dpdklab
2024-03-30 3:56 ` dpdklab
2024-03-30 3:56 ` dpdklab
2024-03-30 3:56 ` dpdklab
2024-03-30 3:56 ` dpdklab
2024-03-30 3:56 ` dpdklab
2024-03-30 3:57 ` dpdklab
2024-03-30 3:58 ` dpdklab
2024-03-30 3:59 ` |FAILURE| " dpdklab
2024-03-30 3:59 ` |SUCCESS| " dpdklab
2024-03-30 3:59 ` dpdklab
2024-03-30 4:00 ` |FAILURE| " dpdklab
2024-03-30 4:01 ` |SUCCESS| " dpdklab
2024-03-30 4:01 ` dpdklab
2024-03-30 4:02 ` |FAILURE| " dpdklab
2024-03-30 4:02 ` |SUCCESS| " dpdklab
2024-03-30 4:02 ` |FAILURE| " dpdklab
2024-03-30 4:03 ` dpdklab
2024-03-30 4:03 ` dpdklab
2024-03-30 4:04 ` |SUCCESS| " dpdklab
2024-03-30 4:05 ` |SUCCESS| pw138995 [PATCH v19 15/15] log: colorize log output 0-day Robot
2024-03-30 4:05 ` |FAILURE| pw138981-138995 [PATCH] [v19,15/15] log: colorize log outp dpdklab
2024-03-30 4:06 ` dpdklab
2024-03-30 4:15 ` dpdklab
2024-03-30 4:15 ` |SUCCESS| " dpdklab
2024-03-30 4:16 ` dpdklab
2024-03-30 4:16 ` dpdklab
2024-03-30 4:16 ` dpdklab
2024-03-30 4:16 ` dpdklab
2024-03-30 4:16 ` dpdklab
2024-03-30 4:17 ` dpdklab
2024-03-30 4:17 ` dpdklab
2024-03-30 4:19 ` dpdklab
2024-03-30 4:19 ` dpdklab
2024-03-30 4:19 ` dpdklab
2024-03-30 4:19 ` |FAILURE| " dpdklab
2024-03-30 4:23 ` |SUCCESS| " dpdklab
2024-03-30 4:40 ` |FAILURE| " dpdklab
2024-03-30 4:40 ` |SUCCESS| " dpdklab
2024-03-30 4:40 ` |FAILURE| " dpdklab
2024-03-30 4:40 ` dpdklab
2024-03-30 4:44 ` dpdklab
2024-03-30 4:44 ` |SUCCESS| " dpdklab
2024-03-30 4:49 ` dpdklab
2024-03-30 4:50 ` dpdklab
2024-03-30 4:51 ` dpdklab
2024-03-30 4:52 ` dpdklab
2024-03-30 4:53 ` dpdklab
2024-03-30 4:56 ` dpdklab
2024-03-30 4:56 ` dpdklab
2024-03-30 4:57 ` dpdklab
2024-03-30 4:59 ` dpdklab
2024-03-30 5:04 ` dpdklab
2024-03-30 5:06 ` dpdklab
2024-03-30 5:27 ` dpdklab
2024-03-30 6:28 ` dpdklab
2024-04-02 23:55 ` dpdklab
2024-04-02 23:59 ` dpdklab
2024-04-03 0:03 ` dpdklab
2024-04-03 0:07 ` dpdklab
2024-04-03 0:26 ` 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=20240330030800.316401223FC@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).