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,
jt@labs.hpe.com, test-report@dpdk.org
Subject: [dpdk-test-report] [Patchwork]|ERROR| pw16868 mempool: Add sanity check when secondary link in less mempools than primary
Date: 28 Oct 2016 11:57:02 -0700 [thread overview]
Message-ID: <959aec$vb3n1d@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 16868
http://www.dpdk.org/dev/patchwork/patch/16868/
Submitter: Jean Tourrilhes <jt@labs.hpe.com>
Date: Fri, 28 Oct 2016 11:37:05 -0700
DPDK git baseline: ca41215c051a1f4f6f96e947ccb671dab3509cbf
Check patch error:
16868:
ERROR: space required before the open parenthesis '('
#56: FILE: lib/librte_mempool/rte_mempool.c:1287:
+ if(mp->ops_index >= (int32_t) rte_mempool_ops_table.num_ops) {
WARNING: braces {} are not necessary for single statement blocks
#59: FILE: lib/librte_mempool/rte_mempool.c:1290:
+ for (i = 0; i < rte_mempool_ops_table.num_ops; i++) {
+ RTE_LOG(ERR, EAL, "Registered mempool[%d] is %s\n", i, rte_mempool_ops_table.ops[i].name);
+ }
WARNING: line over 80 characters
#60: FILE: lib/librte_mempool/rte_mempool.c:1291:
+ RTE_LOG(ERR, EAL, "Registered mempool[%d] is %s\n", i, rte_mempool_ops_table.ops[i].name);
WARNING: line over 80 characters
#63: FILE: lib/librte_mempool/rte_mempool.c:1294:
+ rte_panic("Cannot find ops for mempool, ops_index %d, num_ops %d - maybe due to build process or linker configuration\n", mp->ops_index, rte_mempool_ops_table.num_ops);
total: 1 errors, 3 warnings, 25 lines checked
/home/patchWorkOrg/patches/dpdk-dev-v2-1-1-mempool-Add-sanity-check-when-secondary-link-in-less-mempools-than-primary.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-10-28 18:57 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='959aec$vb3n1d@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=gangx.xu@intel.com \
--cc=huilongx.xu@intel.com \
--cc=jt@labs.hpe.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).