From: sys_stv@intel.com
To: jianbo.liu@linaro.org, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw15286-15290 i40e: extract non-x86 specific code from vector driver
Date: 25 Aug 2016 19:54:55 -0700 [thread overview]
Message-ID: <8dba68$v6tl3t@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1408 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 15286-15290
http://www.dpdk.org/dev/patchwork/patch/15290/
Submitter: Jianbo Liu <jianbo.liu@linaro.org>
Date: Wed, 24 Aug 2016 15:23:41 +0530
DPDK git baseline: 28d8abaf250c3fb4dcb6416518f4c54b4ae67205
Check patch error:
15287:
WARNING: line over 80 characters
#521: FILE: drivers/net/i40e/i40e_rxtx_vec_neon.c:476:
+ ((uint64_t)pkt->data_len << I40E_TXD_QW1_TX_BUF_SZ_SHIFT));
ERROR: need consistent spacing around '*' (ctx:WxV)
#617: FILE: drivers/net/i40e/i40e_rxtx_vec_neon.c:572:
+i40e_txq_vec_setup(struct i40e_tx_queue __rte_unused *txq)
^
total: 1 errors, 1 warnings, 592 lines checked
/home/patchWorkOrg/patches/dpdk-dev-2-5-i40e-implement-vector-PMD-for-ARM-architecture.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-08-26 2:54 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='8dba68$v6tl3t@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=jianbo.liu@linaro.org \
--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).