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,
jerin.jacob@caviumnetworks.com, test-report@dpdk.org
Subject: [dpdk-test-report] [Patchwork]|ERROR| pw16896 libeventdev: event driven programming model framework for DPDK
Date: 02 Nov 2016 05:03:14 -0700 [thread overview]
Message-ID: <532f2c$vliken@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 16896
http://www.dpdk.org/dev/patchwork/patch/16896/
Submitter: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Date: Wed, 2 Nov 2016 16:55:22 +0530
DPDK git baseline: ca41215c051a1f4f6f96e947ccb671dab3509cbf
Check patch error:
16896:
ERROR: patch seems to be corrupt (line wrapped?)
#84: FILE: rte_eventdev.h:428:
rte_event_dev_config *config);
ERROR: Missing Signed-off-by: line(s)
total: 2 errors, 0 warnings, 12 lines checked
/home/patchWorkOrg/patches/dpdk-dev-RFC-v2-libeventdev-event-driven-programming-model-framework-for-DPDK.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-02 12:03 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='532f2c$vliken@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=gangx.xu@intel.com \
--cc=huilongx.xu@intel.com \
--cc=jerin.jacob@caviumnetworks.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).