From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw138795 [PATCH v13 11/11] log: add optional support of syslog
Date: Tue, 26 Mar 2024 03:01:04 +0100 (CET) [thread overview]
Message-ID: <20240326020104.8FC7A1223FA@dpdk.org> (raw)
In-Reply-To: <20240326015827.825648-12-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/138795
_coding style issues_
WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#108: FILE: app/test/test_eal_flags.c:990:
+ const char *argv4[] = {prgname, prefix, mp_flag, "--syslog=both"};
WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#111: FILE: app/test/test_eal_flags.c:992:
+ const char *argv5[] = {prgname, prefix, mp_flag, "--syslog=invalid"};
total: 0 errors, 2 warnings, 194 lines checked
next prev parent reply other threads:[~2024-03-26 2:01 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240326015827.825648-12-stephen@networkplumber.org>
2024-03-26 1:38 ` |SUCCESS| pw138785-138795 " qemudev
2024-03-26 1:42 ` qemudev
2024-03-26 2:01 ` checkpatch [this message]
2024-03-26 2:31 ` |FAILURE| pw138785-138795 [PATCH] [v13,11/11] log: add optional supp dpdklab
2024-03-26 2:33 ` dpdklab
2024-03-26 2:33 ` |SUCCESS| " dpdklab
2024-03-26 2:34 ` dpdklab
2024-03-26 2:34 ` |FAILURE| " dpdklab
2024-03-26 2:34 ` |SUCCESS| " dpdklab
2024-03-26 2:35 ` |FAILURE| " dpdklab
2024-03-26 2:35 ` |SUCCESS| " dpdklab
2024-03-26 2:35 ` dpdklab
2024-03-26 2:36 ` |FAILURE| " dpdklab
2024-03-26 2:36 ` dpdklab
2024-03-26 2:36 ` |SUCCESS| " dpdklab
2024-03-26 2:36 ` dpdklab
2024-03-26 2:37 ` |FAILURE| " dpdklab
2024-03-26 2:37 ` |SUCCESS| " dpdklab
2024-03-26 2:37 ` dpdklab
2024-03-26 2:38 ` |FAILURE| " dpdklab
2024-03-26 2:38 ` dpdklab
2024-03-26 2:38 ` dpdklab
2024-03-26 2:38 ` |SUCCESS| " dpdklab
2024-03-26 2:38 ` dpdklab
2024-03-26 2:38 ` dpdklab
2024-03-26 2:39 ` |FAILURE| " dpdklab
2024-03-26 2:39 ` dpdklab
2024-03-26 2:39 ` |SUCCESS| " dpdklab
2024-03-26 2:39 ` |FAILURE| " dpdklab
2024-03-26 2:39 ` |SUCCESS| " dpdklab
2024-03-26 2:39 ` dpdklab
2024-03-26 2:39 ` dpdklab
2024-03-26 2:39 ` dpdklab
2024-03-26 2:40 ` dpdklab
2024-03-26 2:40 ` dpdklab
2024-03-26 2:40 ` dpdklab
2024-03-26 2:40 ` |FAILURE| " dpdklab
2024-03-26 2:42 ` |SUCCESS| " dpdklab
2024-03-26 2:43 ` dpdklab
2024-03-26 2:44 ` |FAILURE| " dpdklab
2024-03-26 2:45 ` |SUCCESS| " dpdklab
2024-03-26 2:45 ` |FAILURE| " dpdklab
2024-03-26 2:45 ` |SUCCESS| " dpdklab
2024-03-26 2:45 ` dpdklab
2024-03-26 2:45 ` |FAILURE| " dpdklab
2024-03-26 2:46 ` |SUCCESS| " dpdklab
2024-03-26 2:47 ` |FAILURE| " dpdklab
2024-03-26 2:47 ` |SUCCESS| " dpdklab
2024-03-26 2:48 ` dpdklab
2024-03-26 2:48 ` |FAILURE| " dpdklab
2024-03-26 2:48 ` |SUCCESS| " dpdklab
2024-03-26 2:49 ` |FAILURE| " dpdklab
2024-03-26 2:49 ` |SUCCESS| " dpdklab
2024-03-26 2:50 ` dpdklab
2024-03-26 2:50 ` dpdklab
2024-03-26 2:50 ` |FAILURE| " dpdklab
2024-03-26 2:50 ` dpdklab
2024-03-26 2:51 ` |SUCCESS| " dpdklab
2024-03-26 2:51 ` dpdklab
2024-03-26 2:51 ` |FAILURE| " dpdklab
2024-03-26 2:51 ` dpdklab
2024-03-26 2:51 ` dpdklab
2024-03-26 2:52 ` dpdklab
2024-03-26 2:53 ` dpdklab
2024-03-26 2:53 ` dpdklab
2024-03-26 2:53 ` |SUCCESS| " dpdklab
2024-03-26 2:54 ` dpdklab
2024-03-26 2:55 ` |FAILURE| " dpdklab
2024-03-26 2:55 ` |SUCCESS| " dpdklab
2024-03-26 3:00 ` dpdklab
2024-03-26 3:00 ` dpdklab
2024-03-26 3:04 ` |SUCCESS| pw138795 [PATCH v13 11/11] log: add optional support of syslog 0-day Robot
2024-03-26 3:06 ` |FAILURE| pw138785-138795 [PATCH] [v13,11/11] log: add optional supp dpdklab
2024-03-26 3:12 ` |SUCCESS| " dpdklab
2024-03-26 3:35 ` dpdklab
2024-03-26 3:56 ` dpdklab
2024-04-01 19:16 ` dpdklab
2024-04-01 19:20 ` dpdklab
2024-04-01 19:39 ` dpdklab
2024-04-01 19:43 ` dpdklab
2024-04-01 19:47 ` 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=20240326020104.8FC7A1223FA@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).