From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: pablo.de.lara.guarch@intel.com
Subject: [dpdk-test-report] |FAILURE| pw25560 [PATCH v2 04/12] cryptodev: simplify device list retrieval logic
Date: 22 Jun 2017 13:30:39 -0700 [thread overview]
Message-ID: <e81775$12lmudb@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1748 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/25560
_apply patch file failure_
Submitter: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Date: Wed, 21 Jun 2017 07:28:21 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:c687cebe095b2ea325aa012e2834b830f1f74eba
Repo:dpdk-next-crypto, Branch:master, CommitID:b1cac453935eb8d2f1dee8e7ab081711cfb0cf70
Repo:dpdk-next-net, Branch:master, CommitID:4275de7401e1de3252beb14c96909b28024a1b93
Repo:dpdk-next-virtio, Branch:master, CommitID:da5129d9b6b53375667690970f6824565c1f1443
Repo:dpdk, Branch:master, CommitID:8d4d3a4f7337888871be8c52c26a9d6ade96955f
Apply patch file failed:
Repo: dpdk
25560:
patching file lib/librte_cryptodev/rte_cryptodev.c
Hunk #1 FAILED at 511.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.c.rej
Repo: dpdk-next-crypto
25560:
patching file lib/librte_cryptodev/rte_cryptodev.c
Hunk #1 FAILED at 511.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.c.rej
Repo: dpdk-next-net
25560:
patching file lib/librte_cryptodev/rte_cryptodev.c
Hunk #1 FAILED at 511.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.c.rej
Repo: dpdk-next-virtio
25560:
patching file lib/librte_cryptodev/rte_cryptodev.c
Hunk #1 FAILED at 511.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.c.rej
Repo: dpdk-next-eventdev
25560:
patching file lib/librte_cryptodev/rte_cryptodev.c
Hunk #1 FAILED at 511.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_cryptodev/rte_cryptodev.c.rej
DPDK STV team
reply other threads:[~2017-06-22 20:30 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='e81775$12lmudb@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=pablo.de.lara.guarch@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).