From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Subject: [dpdk-test-report] |WARNING| pw24148 [PATCH] vfio: fix device unplug when several devices per vfio group
Date: Mon, 8 May 2017 17:21:47 +0200 (CEST) [thread overview]
Message-ID: <20170508152147.3B8522952@dpdk.org> (raw)
In-Reply-To: <20170508152006.GA28180@jerin>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/24148
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#26:
> > > devices which can not be isolated from other ones are set in same VFIO
ERROR:DIFF_IN_COMMIT_MSG: Avoid using diff content in the commit message - patch(1) might not work
#59:
@@ -266,6 +269,7 @@ vfio_setup_device(const char *sysfs_base, const char
ERROR:CODE_INDENT: code indent should use tabs where possible
#175: FILE: lib/librte_eal/linuxapp/eal/eal_vfio.c:103:
+ printf("###### name %s vfio_group_fd %d
", filename, vfio_group_fd);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#175: FILE: lib/librte_eal/linuxapp/eal/eal_vfio.c:103:
+ printf("###### name %s vfio_group_fd %d
", filename, vfio_group_fd);$
ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#180: FILE: lib/librte_eal/linuxapp/eal/eal_vfio.c:259:
*dev_addr,
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#184: FILE: lib/librte_eal/linuxapp/eal/eal_vfio.c:263:
+ printf("#### iommu_group_fd %d vfio_group_fd=%d
", iommu_group_no, vfio_group_fd);$
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 4 errors, 3 warnings, 15 lines checked
parent reply other threads:[~2017-05-08 15:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170508152006.GA28180@jerin>]
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=20170508152147.3B8522952@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=test-report@dpdk.org \
/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).