From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: hemant.agrawal@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw23373 [PATCH v11 01/22] net/dpaa2: introducing NXP DPAA2 PMD driver
Date: 11 Apr 2017 05:40:53 -0700 [thread overview]
Message-ID: <e624e2$11abh9i@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 7515 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23373
_apply patch file failure_
Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Sun, 9 Apr 2017 13:41:16 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:693772446ce247123f11a1c5bd2d4652cc494cab
Repo:dpdk-next-net, Branch:master, CommitID:50c769ec3d7c6ed8a9680ece4569623439e460f7
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:3c32113a1aac6d399b1850cd24c42df71c1558cd
Apply patch file failed:
Repo: dpdk
23373:
patching file MAINTAINERS
Hunk #1 FAILED at 366.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file config/common_base
Hunk #1 succeeded at 301 with fuzz 1 (offset -10 lines).
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 54.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
patching file drivers/Makefile
Hunk #1 succeeded at 33 with fuzz 2 (offset -2 lines).
can't find file to patch at input line 61
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/bus/Makefile b/drivers/bus/Makefile
|index 1aab1cc..d3a3768 100644
|--- a/drivers/bus/Makefile
|+++ b/drivers/bus/Makefile
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/mempool/Makefile
Hunk #1 FAILED at 33.
1 out of 1 hunk FAILED -- saving rejects to file drivers/mempool/Makefile.rej
patching file drivers/net/Makefile
patching file drivers/net/dpaa2/Makefile
patching file drivers/net/dpaa2/dpaa2_ethdev.c
patching file drivers/net/dpaa2/dpaa2_ethdev.h
patching file drivers/net/dpaa2/rte_pmd_dpaa2_version.map
patching file mk/rte.app.mk
Repo: dpdk-next-crypto
23373:
patching file MAINTAINERS
Hunk #1 FAILED at 366.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file config/common_base
Hunk #1 succeeded at 301 with fuzz 1 (offset -10 lines).
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 54.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
patching file drivers/Makefile
Hunk #1 succeeded at 33 with fuzz 2 (offset -2 lines).
can't find file to patch at input line 61
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/bus/Makefile b/drivers/bus/Makefile
|index 1aab1cc..d3a3768 100644
|--- a/drivers/bus/Makefile
|+++ b/drivers/bus/Makefile
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/mempool/Makefile
Hunk #1 FAILED at 33.
1 out of 1 hunk FAILED -- saving rejects to file drivers/mempool/Makefile.rej
patching file drivers/net/Makefile
patching file drivers/net/dpaa2/Makefile
patching file drivers/net/dpaa2/dpaa2_ethdev.c
patching file drivers/net/dpaa2/dpaa2_ethdev.h
patching file drivers/net/dpaa2/rte_pmd_dpaa2_version.map
patching file mk/rte.app.mk
Repo: dpdk-next-net
23373:
patching file MAINTAINERS
Hunk #1 FAILED at 366.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file config/common_base
Hunk #1 succeeded at 299 with fuzz 1 (offset -12 lines).
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 54.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
patching file drivers/Makefile
Hunk #1 succeeded at 33 with fuzz 2 (offset -2 lines).
can't find file to patch at input line 61
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/bus/Makefile b/drivers/bus/Makefile
|index 1aab1cc..d3a3768 100644
|--- a/drivers/bus/Makefile
|+++ b/drivers/bus/Makefile
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/mempool/Makefile
Hunk #1 FAILED at 33.
1 out of 1 hunk FAILED -- saving rejects to file drivers/mempool/Makefile.rej
patching file drivers/net/Makefile
Hunk #1 succeeded at 51 (offset 2 lines).
patching file drivers/net/dpaa2/Makefile
patching file drivers/net/dpaa2/dpaa2_ethdev.c
patching file drivers/net/dpaa2/dpaa2_ethdev.h
patching file drivers/net/dpaa2/rte_pmd_dpaa2_version.map
patching file mk/rte.app.mk
Hunk #1 succeeded at 114 (offset 1 line).
Hunk #2 succeeded at 167 (offset 1 line).
Repo: dpdk-next-virtio
23373:
patching file MAINTAINERS
Hunk #1 FAILED at 366.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file config/common_base
Hunk #1 succeeded at 301 with fuzz 1 (offset -10 lines).
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 54.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
patching file drivers/Makefile
Hunk #1 succeeded at 33 with fuzz 2 (offset -2 lines).
can't find file to patch at input line 61
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/bus/Makefile b/drivers/bus/Makefile
|index 1aab1cc..d3a3768 100644
|--- a/drivers/bus/Makefile
|+++ b/drivers/bus/Makefile
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/mempool/Makefile
Hunk #1 FAILED at 33.
1 out of 1 hunk FAILED -- saving rejects to file drivers/mempool/Makefile.rej
patching file drivers/net/Makefile
Hunk #1 succeeded at 44 (offset -5 lines).
patching file drivers/net/dpaa2/Makefile
patching file drivers/net/dpaa2/dpaa2_ethdev.c
patching file drivers/net/dpaa2/dpaa2_ethdev.h
patching file drivers/net/dpaa2/rte_pmd_dpaa2_version.map
patching file mk/rte.app.mk
Repo: dpdk-next-eventdev
23373:
patching file MAINTAINERS
Hunk #1 FAILED at 366.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file config/common_base
Hunk #1 succeeded at 292 with fuzz 1 (offset -19 lines).
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 54.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
patching file drivers/Makefile
Hunk #1 succeeded at 33 with fuzz 2 (offset -2 lines).
can't find file to patch at input line 61
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/bus/Makefile b/drivers/bus/Makefile
|index 1aab1cc..d3a3768 100644
|--- a/drivers/bus/Makefile
|+++ b/drivers/bus/Makefile
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/mempool/Makefile
Hunk #1 FAILED at 33.
1 out of 1 hunk FAILED -- saving rejects to file drivers/mempool/Makefile.rej
patching file drivers/net/Makefile
Hunk #1 succeeded at 42 (offset -7 lines).
patching file drivers/net/dpaa2/Makefile
patching file drivers/net/dpaa2/dpaa2_ethdev.c
patching file drivers/net/dpaa2/dpaa2_ethdev.h
patching file drivers/net/dpaa2/rte_pmd_dpaa2_version.map
patching file mk/rte.app.mk
Hunk #1 succeeded at 110 (offset -3 lines).
Hunk #2 succeeded at 159 (offset -7 lines).
DPDK STV team
reply other threads:[~2017-04-11 12:40 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$11abh9i@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=hemant.agrawal@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).