From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Pei, Yulong" <yulong.pei@intel.com>
Subject: [dpdk-test-report] |WARNING| pw23898 [PATCH] app/testpmd: initalize port_numa and ring_numa
Date: Wed, 26 Apr 2017 12:36:42 +0200 (CEST) [thread overview]
Message-ID: <20170426103642.2F8C52C50@dpdk.org> (raw)
In-Reply-To: <1493181063-14145-1-git-send-email-yulong.pei@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/23898
_coding style issues_
WARNING:TYPO_SPELLING: 'initalize' may be misspelled - perhaps 'initialize'?
#5:
Subject: [dpdk-dev] [PATCH] app/testpmd: initalize port_numa and ring_numa
WARNING:TYPO_SPELLING: 'initalized' may be misspelled - perhaps 'initialized'?
#15:
command line to enable numa, so port_numa and ring_numa were initalized
WARNING:TYPO_SPELLING: 'initalize' may be misspelled - perhaps 'initialize'?
#17:
default, so port_numa and ring_numa also need to initalize by default,
ERROR:SPACING: space required after that ',' (ctx:VxV)
#53: FILE: app/test-pmd/testpmd.c:547:
+ memset(port_numa,NUMA_NO_CONFIG,RTE_MAX_ETHPORTS);
^
ERROR:SPACING: space required after that ',' (ctx:VxV)
#53: FILE: app/test-pmd/testpmd.c:547:
+ memset(port_numa,NUMA_NO_CONFIG,RTE_MAX_ETHPORTS);
^
ERROR:SPACING: space required after that ',' (ctx:VxV)
#54: FILE: app/test-pmd/testpmd.c:548:
+ memset(rxring_numa,NUMA_NO_CONFIG,RTE_MAX_ETHPORTS);
^
ERROR:SPACING: space required after that ',' (ctx:VxV)
#54: FILE: app/test-pmd/testpmd.c:548:
+ memset(rxring_numa,NUMA_NO_CONFIG,RTE_MAX_ETHPORTS);
^
ERROR:SPACING: space required after that ',' (ctx:VxV)
#55: FILE: app/test-pmd/testpmd.c:549:
+ memset(txring_numa,NUMA_NO_CONFIG,RTE_MAX_ETHPORTS);
^
ERROR:SPACING: space required after that ',' (ctx:VxV)
#55: FILE: app/test-pmd/testpmd.c:549:
+ memset(txring_numa,NUMA_NO_CONFIG,RTE_MAX_ETHPORTS);
^
total: 6 errors, 3 warnings, 25 lines checked
parent reply other threads:[~2017-04-26 10:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1493181063-14145-1-git-send-email-yulong.pei@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=20170426103642.2F8C52C50@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=yulong.pei@intel.com \
/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).