From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: wangzhike <wangzhike@jd.com>
Subject: [dpdk-test-report] |WARNING| pw32848 [PATCH] net/virtio: fix vector Rx break caused by rxq flushing
Date: Wed, 3 Jan 2018 09:22:53 +0100 (CET) [thread overview]
Message-ID: <20180103082253.1BE471B1AA@dpdk.org> (raw)
In-Reply-To: <6DAF063A35010343823807B082E5681F41D84163@mbx05.360buyAD.local>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/32848
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#20:
You mentioned that " Otherwise it will lead to incorrect packet collection for port state." Do you mean port statistics? Or such packets may leads to issue, like more TCP restransmission? Thanks.
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#23:
commit d8227497ec5c3de75fe378e09fc9673ae097fa73
ERROR:BAD_SIGN_OFF: Unrecognized email address: '王志克\r'
#41:
To: 王志克
ERROR:DIFF_IN_COMMIT_MSG: Avoid using diff content in the commit message - patch(1) might not work
#86:
--- a/drivers/net/virtio/virtqueue.c
ERROR:DOS_LINE_ENDINGS: DOS line endings
#93: FILE: drivers/net/virtio/virtqueue.c:91:
+^I^Iif (hw->use_simple_rxtx) {^M$
ERROR:DOS_LINE_ENDINGS: DOS line endings
#102: FILE: drivers/net/virtio/virtqueue.c:107:
+^Iif (hw->use_simple_rxtx) {^M$
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 6 errors, 1 warnings, 0 checks, 16 lines checked
parent reply other threads:[~2018-01-03 8:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6DAF063A35010343823807B082E5681F41D84163@mbx05.360buyAD.local>]
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=20180103082253.1BE471B1AA@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=wangzhike@jd.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).