From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: John Levon <john.levon@nutanix.com>
Subject: [dpdk-test-report] |WARNING| pw96729 [PATCH] eal: allow hugetlbfs sub-directories
Date: Mon, 9 Aug 2021 13:26:12 +0200 (CEST) [thread overview]
Message-ID: <20210809112612.371261209D4@dpdk.org> (raw)
In-Reply-To: <20210809112434.383123-1-john.levon@nutanix.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/96729
_coding style issues_
WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#131: FILE: app/test/test_eal_flags.c:904:
+ const char *argv10[] = {prgname, "-m", DEFAULT_MEM_SIZE,
WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#134: FILE: app/test/test_eal_flags.c:907:
+ const char *argv11[] = {prgname, "-m", DEFAULT_MEM_SIZE,
WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#139: FILE: app/test/test_eal_flags.c:911:
+ const char *argv12[] = {prgname, prefix, mp_flag,
WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#144: FILE: app/test/test_eal_flags.c:915:
+ const char *argv13[] = {prgname, "--file-prefix=virtaddr",
WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#149: FILE: app/test/test_eal_flags.c:919:
+ const char *argv14[] = {prgname, "--file-prefix=intr",
WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#154: FILE: app/test/test_eal_flags.c:923:
+ const char *argv15[] = {prgname, "--file-prefix=intr",
WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#159: FILE: app/test/test_eal_flags.c:927:
+ const char *argv16[] = {prgname, "--file-prefix=intr",
WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#164: FILE: app/test/test_eal_flags.c:931:
+ const char *argv17[] = {prgname, "--file-prefix=intr",
total: 0 errors, 8 warnings, 356 lines checked
next parent reply other threads:[~2021-08-09 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210809112434.383123-1-john.levon@nutanix.com>
2021-08-09 11:26 ` checkpatch [this message]
2021-08-09 11:58 ` [dpdk-test-report] |SUCCESS| pw96729 [dpdk-dev] " 0-day Robot
2021-08-09 11:50 [dpdk-test-report] |WARNING| pw96729 " 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=20210809112612.371261209D4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=john.levon@nutanix.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).