From: sys_stv@intel.com
To: viktorin@rehivetech.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw14690-14704 eal: no need to test for PMD_VDEV anymore
Date: 13 Jul 2016 20:20:22 -0700 [thread overview]
Message-ID: <8dba68$ue0402@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 14690-14704
http://www.dpdk.org/dev/patchwork/patch/14691/
Submitter: Jan Viktorin <viktorin@rehivetech.com>
Date: Fri, 8 Jul 2016 21:09:31 +0200
DPDK git baseline: 11c5e45d88ff3fcb86be4a1c23c766b35bafdc70
Check patch:Success
patch file error:
14691:
patching file lib/librte_eal/bsdapp/eal/Makefile
patching file lib/librte_eal/common/Makefile patching file lib/librte_eal/common/eal_common_dev.c
Hunk #3 FAILED at 99.
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_dev.c.rej
patching file lib/librte_eal/common/eal_common_vdev.c
patching file lib/librte_eal/common/include/rte_dev.h
Hunk #1 succeeded at 203 with fuzz 2 (offset -7 lines).
patching file lib/librte_eal/common/include/rte_vdev.h
patching file lib/librte_eal/linuxapp/eal/Makefile
DPDK STV team
reply other threads:[~2016-07-14 3:20 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$ue0402@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=viktorin@rehivetech.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).