From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Tonghao Zhang <xiangxia.m.yue@gmail.com>
Subject: [dpdk-test-report] |WARNING| pw36781 [PATCH] Build is broken in dpdk-next-net
Date: Fri, 30 Mar 2018 16:48:21 +0200 (CEST) [thread overview]
Message-ID: <20180330144821.621547260@dpdk.org> (raw)
In-Reply-To: <CAMDZJNV62FL7WMgPsy0+pMYT47gDNV3vidFSRJqAix9bGHe1OQ@mail.gmail.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/36781
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#17:
I rebuild it on ubuntu 17.10 and cash it. I use the 'RTE_SET_USED' to fix it.
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#67:
>> > ad94ade905454401b705be9e06b19e54a1c78148 vhost: add pipe event for
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#95: FILE: lib/librte_vhost/fd_man.c:282:
+ int r = read(readfd, charbuf, sizeof(charbuf));$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#96: FILE: lib/librte_vhost/fd_man.c:283:
+ RTE_SET_USED(r);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#105: FILE: lib/librte_vhost/fd_man.c:323:
+ int r = write(fdset->u.writefd, "1", 1);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#106: FILE: lib/librte_vhost/fd_man.c:324:
+ RTE_SET_USED(r);$
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 2 errors, 5 warnings, 16 lines checked
parent reply other threads:[~2018-03-30 14:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAMDZJNV62FL7WMgPsy0+pMYT47gDNV3vidFSRJqAix9bGHe1OQ@mail.gmail.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=20180330144821.621547260@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=xiangxia.m.yue@gmail.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).