From: sys_stv@intel.com
To: roy.fan.zhang@intel.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw15269-15270 examples/ipsec-secgw: add configuration file support
Date: 25 Aug 2016 19:32:43 -0700 [thread overview]
Message-ID: <8dba68$v6teee@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 15269-15270
http://www.dpdk.org/dev/patchwork/patch/15270/
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Tue, 23 Aug 2016 15:46:48 +0100
DPDK git baseline: b3aaf05cd7ae39a16c386d8f9a9a686753fdae92
Check patch error:
15269:
ERROR: spaces required around that '?' (ctx:VxV)
#2819: FILE: examples/ipsec-secgw/sa.c:454:
+ printf(" spi_%s(%3u):", inbound?"in":"out", sa->spi);
^
ERROR: spaces required around that ':' (ctx:VxV)
#2819: FILE: examples/ipsec-secgw/sa.c:454:
+ printf(" spi_%s(%3u):", inbound?"in":"out", sa->spi);
^
total: 2 errors, 0 warnings, 4030 lines checked
/home/patchWorkOrg/patches/dpdk-dev-v6-1-2-examples-ipsec-secgw-add-configuration-file-support.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:32 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$v6teee@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=roy.fan.zhang@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).