automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: John Levon <john.levon@nutanix.com>
Subject: [dpdk-test-report] |WARNING| pw101243 [PATCH] eal/linux: allow hugetlbfs sub-directories
Date: Tue, 12 Oct 2021 18:06:27 +0200 (CEST)	[thread overview]
Message-ID: <20211012160627.56CE1120E00@dpdk.org> (raw)
In-Reply-To: <20211012160520.1276061-1-john.levon@nutanix.com>

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

_coding style issues_


WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#136: 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
#139: 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
#144: 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
#149: 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
#154: 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
#159: 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
#164: 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
#169: FILE: app/test/test_eal_flags.c:931:
+	const char *argv17[] = {prgname, "--file-prefix=intr",

total: 0 errors, 8 warnings, 374 lines checked

       reply	other threads:[~2021-10-12 16:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211012160520.1276061-1-john.levon@nutanix.com>
2021-10-12 16:06 ` checkpatch [this message]
2021-10-12 16:59 ` [dpdk-test-report] |SUCCESS| pw101243 [dpdk-dev] " 0-day Robot
2021-10-12 16:28 [dpdk-test-report] |WARNING| pw101243 " 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=20211012160627.56CE1120E00@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).