From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anatoly Burakov <anatoly.burakov@intel.com>
Subject: [dpdk-test-report] |WARNING| pw48117 test: fix eal flags autotest hugepage file handling
Date: Thu, 15 Nov 2018 13:19:21 +0100 (CET) [thread overview]
Message-ID: <20181115121921.30DD14F90@dpdk.org> (raw)
In-Reply-To: <532f05a13228ffd85931807dd4aa2384a27b7da4.1542283782.git.anatoly.burakov@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/48117
_coding style issues_
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#22:
When 3f9e31d71d63 ("test: clean up on exit") was introduced, the
WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#87: FILE: test/test/test_eal_flags.c:980:
+ const char *argv1[] = {prgname, "-c", "1", "-n", "2", "-m",
WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#94: FILE: test/test/test_eal_flags.c:984:
+ const char *argv2[] = {prgname, "-c", "1", "-n", "2", "-m",
WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#99: FILE: test/test/test_eal_flags.c:989:
+ const char *argv3[] = {prgname, "-c", "1", "-n", "2", "-m",
WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#104: FILE: test/test/test_eal_flags.c:994:
+ const char *argv4[] = {prgname, "-c", "1", "-n", "2", "-m",
total: 1 errors, 4 warnings, 132 lines checked
parent reply other threads:[~2018-11-15 12:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <532f05a13228ffd85931807dd4aa2384a27b7da4.1542283782.git.anatoly.burakov@intel.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=20181115121921.30DD14F90@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=anatoly.burakov@intel.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).