automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stanislaw Kardach <kda@semihalf.com>
Subject: [dpdk-test-report] |WARNING| pw91112 [PATCH 2/3] test: disable no-huge where it's not necessary
Date: Mon, 12 Apr 2021 12:07:16 +0200 (CEST)	[thread overview]
Message-ID: <20210412100716.8BCB61208AA@dpdk.org> (raw)
In-Reply-To: <20210412100645.668395-3-kda@semihalf.com>

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

_coding style issues_


WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#129: FILE: app/test/test_eal_flags.c:368:
+	const char *vdevinval[] = {prgname, prefix, no_huge_compat,

WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#134: FILE: app/test/test_eal_flags.c:372:
+	const char *vdevval1[] = {prgname, prefix, no_huge_compat,

WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#138: FILE: app/test/test_eal_flags.c:375:
+	const char *vdevval2[] = {prgname, prefix, no_huge_compat,

WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#142: FILE: app/test/test_eal_flags.c:378:
+	const char *vdevval3[] = {prgname, prefix, no_huge_compat,

WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#151: FILE: app/test/test_eal_flags.c:688:
+	const char *argv1[] = { prgname, prefix, no_huge_compat, no_shconf,

WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#155: FILE: app/test/test_eal_flags.c:691:
+	const char *argv2[] = { prgname, prefix, no_huge_compat, no_shconf,

WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#159: FILE: app/test/test_eal_flags.c:694:
+	const char *argv3[] = { prgname, prefix, no_huge_compat, no_shconf,

WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#163: FILE: app/test/test_eal_flags.c:697:
+	const char *argv4[] = { prgname, prefix, no_huge_compat, no_shconf,

WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#167: FILE: app/test/test_eal_flags.c:700:
+	const char *argv5[] = { prgname, prefix, no_huge_compat, no_shconf};

total: 0 errors, 9 warnings, 78 lines checked

           reply	other threads:[~2021-04-12 10:07 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20210412100645.668395-3-kda@semihalf.com>]

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=20210412100716.8BCB61208AA@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=kda@semihalf.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).