From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: jerin.jacob@caviumnetworks.com
Subject: [dpdk-test-report] |FAILURE| pw19306 [PATCH v3 15/29] crypto/qat: use eal I/O device memory read/write API
Date: 13 Jan 2017 03:10:13 -0800 [thread overview]
Message-ID: <e624e2$108c98c@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
Test-Label: Intel compilation
Test-Status: FAILURE
http://dpdk.org/patch/19306
_apply patch file failure_
Submitter: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Date: Fri, 13 Jan 2017 13:47:05 +0530 Mon Dec 5 06:36:49 2016 +0530
DPDK git baseline: Repo:dpdk-next-crypto, Branch:master, CommitID:466aa3996538aca2f1a06804a51d648f68a929e9
Apply patch file failed:
Repo: dpdk-next-crypto
19306:
patching file lib/librte_eal/common/include/arch/x86/rte_atomic.h
Hunk #1 FAILED at 61.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/include/arch/x86/rte_atomic.h.rej
Repo: dpdk-next-net
19306:
patching file lib/librte_eal/common/include/arch/x86/rte_atomic.h
Hunk #1 FAILED at 61.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/include/arch/x86/rte_atomic.h.rej
Repo: dpdk-next-virtio
19306:
patching file lib/librte_eal/common/include/arch/x86/rte_atomic.h
Hunk #1 FAILED at 61.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/include/arch/x86/rte_atomic.h.rej
Repo: dpdk
19306:
patching file lib/librte_eal/common/include/arch/x86/rte_atomic.h
Hunk #1 FAILED at 61.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/include/arch/x86/rte_atomic.h.rej
DPDK STV team
reply other threads:[~2017-01-13 11:10 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='e624e2$108c98c@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=jerin.jacob@caviumnetworks.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).