From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Subject: [dpdk-test-report] |WARNING| pw23640 [PATCH] vhost: avoid memory write on net header when necessary
Date: Fri, 14 Apr 2017 09:56:28 +0200 (CEST) [thread overview]
Message-ID: <20170414075628.50F335598@dpdk.org> (raw)
In-Reply-To: <1492156398-14405-1-git-send-email-yuanhan.liu@linux.intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/23640
_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")'
#18:
[0]: c9ea670c1dc7 ("net/virtio: fix performance regression due to TSO")
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#19:
[1]: 16994abee215 ("net/virtio: optimize header reset on any layout")
WARNING:TYPO_SPELLING: 'mergable' may be misspelled - perhaps 'mergeable'?
#23:
the gap between the mergeable Rx and non-mergable Rx is pretty small now:
total: 2 errors, 1 warnings, 89 lines checked
parent reply other threads:[~2017-04-14 7:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1492156398-14405-1-git-send-email-yuanhan.liu@linux.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=20170414075628.50F335598@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=yuanhan.liu@linux.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).