From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: akhil.goyal@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw18444 [PATCH v2 08/11] crypto/dpaa2_sec: Enable DPAA2_SEC PMD in the configuration
Date: 22 Dec 2016 08:22:37 -0800 [thread overview]
Message-ID: <587443$kmpeg@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
Test-Label: Intel compilation
Test-Status: FAILURE
http://dpdk.org/patch/18444
_apply patch file failure_
Submitter: Akhil Goyal <akhil.goyal@nxp.com>
Date: Fri, 23 Dec 2016 01:46:57 +0530
DPDK git baseline: Repo:dpdk-next-crypto, Branch:master, CommitID:5123faf0c077c71a726c13c618483010352927e9
Repo:dpdk-next-net, Branch:master, CommitID:bb2eefe9d788c91cc3b6e3a867f89b296fcb3d32
Repo:dpdk-next-virtio, Branch:master, CommitID:584b07eea17fbd5977df4301baae114494855d64
Repo:dpdk, Branch:master, CommitID:15925897e7fafd46ecea707b30a875fb3f6c8ddd
Apply patch file failed:
Repo: dpdk-next-crypto
18444:
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 66.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
Repo: dpdk-next-net
18444:
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 66.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
Repo: dpdk-next-virtio
18444:
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 66.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
Repo: dpdk
18444:
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 66.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
DPDK STV team
reply other threads:[~2016-12-22 16:22 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='587443$kmpeg@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=akhil.goyal@nxp.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).