From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: akhil.goyal@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw17676 [PATCH, 5/8] crypto/dpaa2_sec: debug and log support
Date: 06 Dec 2016 17:31:27 -0800 [thread overview]
Message-ID: <9ddf0d$10kruc2@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3690 bytes --]
Test-Label: Intel Per-patch compilation check
Test-Status: FAILURE
Patchwork ID: 17676
http://www.dpdk.org/dev/patchwork/patch/17676
Submitter: Akhil Goyal <akhil.goyal@nxp.com>
Date: Mon, 5 Dec 2016 18:25:37 +0530
DPDK git baseline: Repo:dpdk-next-crypto, Branch:master, CommitID:e6c7b6ec57f3527ce55fa3e0d2a8ed1533722253
Repo:dpdk-next-net, Branch:master, CommitID:4426a902385b655a9981a7a82cfcba6055738e63
Repo:dpdk-next-virtio, Branch:master, CommitID:b5415fbc69dd33a1bb64a140b2f6bc73d11e4d22
Repo:dpdk, Branch:master, CommitID:5d8f0baf69ea1462c8cc32729c789f7278bf3dc2
Apply patch file failed:
Repo: dpdk-next-crypto
17676:
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 56.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
can't find file to patch at input line 39
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
|index 46e3571..83b9b61 100644
|--- a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
|+++ b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
4 out of 4 hunks ignored
patching file drivers/crypto/dpaa2_sec/dpaa2_sec_logs.h
Repo: dpdk-next-net
17676:
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 56.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
can't find file to patch at input line 39
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
|index 46e3571..83b9b61 100644
|--- a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
|+++ b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
4 out of 4 hunks ignored
patching file drivers/crypto/dpaa2_sec/dpaa2_sec_logs.h
Repo: dpdk-next-virtio
17676:
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 56.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
can't find file to patch at input line 39
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
|index 46e3571..83b9b61 100644
|--- a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
|+++ b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
4 out of 4 hunks ignored
patching file drivers/crypto/dpaa2_sec/dpaa2_sec_logs.h
Repo: dpdk
17676:
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 56.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
can't find file to patch at input line 39
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
|index 46e3571..83b9b61 100644
|--- a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
|+++ b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
4 out of 4 hunks ignored
patching file drivers/crypto/dpaa2_sec/dpaa2_sec_logs.h
DPDK STV team
reply other threads:[~2016-12-07 1:31 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='9ddf0d$10kruc2@fmsmga002.fm.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).