From: sys_stv@intel.com
To: yongjiex.gu@intel.com, weichunx.chen@intel.com,
huilongx.xu@intel.com, gangx.xu@intel.com, peipeix.lu@intel.com,
lei.a.yao@intel.com, test-report@dpdk.org
Subject: [dpdk-test-report] [Patchwork]|ERROR| pw16981 examples/l3fwd: force CRC stripping for i40evf
Date: 09 Nov 2016 17:35:46 -0800 [thread overview]
Message-ID: <9ddf0d$108uglo@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1849 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 16981
http://www.dpdk.org/dev/patchwork/patch/16981/
Submitter: "Yao, Lei A" <lei.a.yao@intel.com>
Date: Wed, 9 Nov 2016 08:37:36 +0000
DPDK git baseline: a4366ade74de491f008224bc2af2c75bea68e4a9
Check patch error:
16981:
ERROR: DOS line endings
#48: FILE: examples/l3fwd/main.c:909:
+^I^Irte_eth_dev_info_get(portid, &dev_info);^M$
ERROR: DOS line endings
#49: FILE: examples/l3fwd/main.c:910:
+^I^Iif (dev_info.driver_name &&^M$
ERROR: DOS line endings
#50: FILE: examples/l3fwd/main.c:911:
+^I^I strcmp(dev_info.driver_name, "net_i40e_vf") == 0) {^M$
ERROR: DOS line endings
#51: FILE: examples/l3fwd/main.c:912:
+^I^I^I/* i40evf require that CRC stripping is enabled. */^M$
ERROR: DOS line endings
#52: FILE: examples/l3fwd/main.c:913:
+^I^I^Iport_conf.rxmode.hw_strip_crc = 1;^M$
ERROR: DOS line endings
#53: FILE: examples/l3fwd/main.c:914:
+^I^I} else {^M$
ERROR: DOS line endings
#54: FILE: examples/l3fwd/main.c:915:
+^I^I^Iport_conf.rxmode.hw_strip_crc = 0;^M$
ERROR: DOS line endings
#55: FILE: examples/l3fwd/main.c:916:
+^I^I}^M$
total: 8 errors, 0 warnings, 21 lines checked
/home/patchWorkOrg/patches/dpdk-dev-examples-l3fwd-force-CRC-stripping-for-i40evf.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
reply other threads:[~2016-11-10 1:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='9ddf0d$108uglo@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=gangx.xu@intel.com \
--cc=huilongx.xu@intel.com \
--cc=lei.a.yao@intel.com \
--cc=peipeix.lu@intel.com \
--cc=test-report@dpdk.org \
--cc=weichunx.chen@intel.com \
--cc=yongjiex.gu@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).