From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: yuan peng <yuan.peng@intel.com>
Subject: [dpdk-test-report] |WARNING| pw32059 [PATCH v7] net/i40e: determine number of queues per VF during run time
Date: Mon, 11 Dec 2017 03:34:22 +0100 (CET) [thread overview]
Message-ID: <20171211023422.042317D26@dpdk.org> (raw)
In-Reply-To: <67D543A150B29E4CAAE53918F64EDAEA3746081F@SHSMSX103.ccr.corp.intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/32059
_coding style issues_
WARNING:BAD_SIGN_OFF: email address 'Peng,Yuan<yuan.peng@intel.com>' might be better as '"Peng,Yuan" <yuan.peng@intel.com>'
#17:
Tested-by: Peng,Yuan<yuan.peng@intel.com>
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#20:
- Tested Commit: 224374cc0e3ca44af5141fb7035a97f338d00c18
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#45:
pf->fc_conf.high_water[I40E_MAX_TRAFFIC_CLASS] = I40E_DEFAULT_HIGH_WATER; @@ -3992,7 +4056,6 @@ i40e_pf_parameter_init(struct rte_eth_dev *dev)
ERROR:DIFF_IN_COMMIT_MSG: Avoid using diff content in the commit message - patch(1) might not work
#53:
@@ -4022,7 +4085,7 @@ i40e_pf_parameter_init(struct rte_eth_dev *dev)
WARNING:TYPO_SPELLING: 'Lauch' may be misspelled - perhaps 'Launch'?
#166:
Lauch the VM with the VF PCI passthrough::
ERROR:OPEN_BRACE: open brace '{' following function declarations go on the next line
#297: FILE: drivers/net/i40e/i40e_ethdev.c:4006:
+static int i40e_pf_config_vf_rxq_number(struct rte_eth_dev *dev) {
total: 3 errors, 3 warnings, 0 checks, 74 lines checked
parent reply other threads:[~2017-12-11 2:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <67D543A150B29E4CAAE53918F64EDAEA3746081F@SHSMSX103.ccr.corp.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=20171211023422.042317D26@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=yuan.peng@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).