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,
shreyansh.jain@nxp.com, test-report@dpdk.org
Subject: [dpdk-test-report] [Patchwork]|ERROR| pw16817-16836 eal: generalize PCI kernel driver enum to EAL
Date: 27 Oct 2016 18:26:21 -0700 [thread overview]
Message-ID: <532f2c$vj84cc@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2413 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 16817-16836
http://www.dpdk.org/dev/patchwork/patch/16836/
Submitter: Shreyansh Jain <shreyansh.jain@nxp.com>
Date: Thu, 27 Oct 2016 20:47:27 +0530
DPDK git baseline: ca41215c051a1f4f6f96e947ccb671dab3509cbf
Check patch:Success
patch file error:
16827:
patching file lib/librte_eal/common/eal_common_dev.c
patching file lib/librte_eal/common/eal_common_devargs.c
patching file lib/librte_eal/common/eal_common_soc.c
Hunk #1 FAILED at 37.
Hunk #2 FAILED at 70.
Hunk #3 FAILED at 85.
Hunk #4 FAILED at 129.
Hunk #5 FAILED at 233.
5 out of 5 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_soc.c.rej
patching file lib/librte_eal/common/include/rte_devargs.h
patching file lib/librte_eal/common/include/rte_soc.h
Hunk #1 FAILED at 164.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/include/rte_soc.h.rej
16836:
patching file lib/librte_cryptodev/rte_cryptodev.c
Hunk #1 succeeded at 443 (offset 21 lines).
Hunk #2 succeeded at 514 (offset 24 lines).
Hunk #3 succeeded at 561 with fuzz 2 (offset 46 lines).
Hunk #4 FAILED at 975.
1 out of 4 hunks FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.c.rej
patching file lib/librte_cryptodev/rte_cryptodev.h
Hunk #1 succeeded at 231 (offset -13 lines).
Hunk #2 succeeded at 611 (offset -13 lines).
patching file lib/librte_cryptodev/rte_cryptodev_pmd.h
Hunk #2 succeeded at 130 (offset -2 lines).
Hunk #3 succeeded at 538 with fuzz 2 (offset 17 lines).
patching file lib/librte_cryptodev/rte_cryptodev_version.map
Hunk #1 FAILED at 44.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev_version.map.rej
16835:
patching file lib/librte_ether/rte_ethdev.c
Hunk #1 succeeded at 363 (offset 38 lines).
Hunk #2 succeeded at 1832 (offset 180 lines).
Hunk #3 succeeded at 2807 (offset 176 lines).
Hunk #4 succeeded at 2852 (offset 176 lines).
Hunk #5 FAILED at 2700.
Hunk #6 succeeded at 3525 with fuzz 1 (offset 176 lines).
1 out of 6 hunks FAILED -- saving rejects to file lib/librte_ether/rte_ethdev.c.rej
patching file lib/librte_ether/rte_ethdev.h
Hunk #2 succeeded at 871 (offset -7 lines).
Hunk #3 succeeded at 1632 (offset 4 lines).
Hunk #4 succeeded at 1868 (offset 5 lines).
Hunk #5 succeeded at 4274 (offset 8 lines).
Hunk #6 succeeded at 4387 with fuzz 2 (offset -7 lines).
DPDK STV team
reply other threads:[~2016-10-28 1:26 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$vj84cc@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=gangx.xu@intel.com \
--cc=huilongx.xu@intel.com \
--cc=peipeix.lu@intel.com \
--cc=shreyansh.jain@nxp.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).