From: sys_stv@intel.com
To: huawei.xie@intel.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw12462 virtio still blindly take over virtio device managed by kernel
Date: 10 May 2016 02:44:15 -0700 [thread overview]
Message-ID: <acb6cf$t34n7m@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2202 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 12462
http://www.dpdk.org/dev/patchwork/patch/12462/
Submitter: Huawei Xie <huawei.xie@intel.com>
Date: Fri, 6 May 2016 08:30:26 +0000
DPDK git baseline: db340cf2ef71af231af67be8e42fd603e4bab0ac
Check patch error:
12462:
WARNING: email address 'Vincent Li <vincent.mc.li@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>,' might be better as '"Vincent Li <vincent.mc.li@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>,'
#10:
To: Vincent Li <vincent.mc.li@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>,
ERROR: patch seems to be corrupt (line wrapped?)
#93: FILE: drivers/net/virtio/virtio_pci.c:649:
virtio_hw *hw)
ERROR: code indent should use tabs where possible
#98: FILE: drivers/net/virtio/virtio_pci.c:653:
+ (!dev->devargs ||$
WARNING: please, no spaces at the start of a line
#98: FILE: drivers/net/virtio/virtio_pci.c:653:
+ (!dev->devargs ||$
ERROR: code indent should use tabs where possible
#99: FILE: drivers/net/virtio/virtio_pci.c:654:
+ dev->devargs->type !=
+ RTE_DEVTYPE_WHITELISTED_PCI)){$
WARNING: please, no spaces at the start of a line
#99: FILE: drivers/net/virtio/virtio_pci.c:654:
+ dev->devargs->type !=
+ RTE_DEVTYPE_WHITELISTED_PCI)){$
ERROR: Missing Signed-off-by: line(s)
total: 4 errors, 3 warnings, 9 lines checked
NOTE: whitespace errors detected, you may wish to use scripts/cleanpatch or
scripts/cleanfile
/home/patchWorkOrg/patches/dpdk-dev-virtio-still-blindly-take-over-virtio-device-managed-by-kernel.patch has style problems, please review.
If any of these errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS.
Compilation:
OS: fedora
Nic: niantic
GCC: gcc_x86-64, 4.8.3
ICC:16.0.2
i686-native-linuxapp-icc: compile pass
x86_64-native-linuxapp-gcc-combined: compile pass
i686-native-linuxapp-gcc: compile pass
x86_64-native-linuxapp-gcc: compile pass
x86_64-native-linuxapp-icc: compile pass
x86_64-native-linuxapp-gcc-debug: compile pass
x86_64-native-linuxapp-gcc-shared: compile pass
x86_64-native-linuxapp-clang: compile pass
DPDK STV team
next reply other threads:[~2016-05-10 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 9:44 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-10 9:32 sys_stv
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='acb6cf$t34n7m@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=huawei.xie@intel.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).