automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: hemant.agrawal@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw23372 [PATCH v2] mempool/dpaa2: add DPAA2 hardware offloaded mempool
Date: 11 Apr 2017 04:56:38 -0700	[thread overview]
Message-ID: <e81775$11pcnnt@fmsmga001.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 6004 bytes --]

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23372

_apply patch file failure_

Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Sun, 9 Apr 2017 13:29:46 +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:1982dbd33836f8cc26b66fe8c4753439283baca7
Apply patch file failed:
Repo: dpdk
23372:
patching file MAINTAINERS
Hunk #1 FAILED at 367.
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 -5 lines).
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 succeeded at 35 with fuzz 2 (offset -7 lines).
patching file drivers/Makefile
Hunk #1 succeeded at 32 with fuzz 2 (offset -1 lines).
can't find file to patch at input line 64
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 a0725ac..1aab1cc 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
patching file drivers/mempool/dpaa2/Makefile
patching file drivers/mempool/dpaa2/dpaa2_hw_mempool.c
patching file drivers/mempool/dpaa2/dpaa2_hw_mempool.h
patching file drivers/mempool/dpaa2/rte_mempool_dpaa2_version.map

Repo: dpdk-next-crypto
23372:
patching file MAINTAINERS
Hunk #1 FAILED at 367.
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 -5 lines).
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 succeeded at 35 with fuzz 2 (offset -7 lines).
patching file drivers/Makefile
Hunk #1 succeeded at 32 with fuzz 2 (offset -1 lines).
can't find file to patch at input line 64
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 a0725ac..1aab1cc 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
patching file drivers/mempool/dpaa2/Makefile
patching file drivers/mempool/dpaa2/dpaa2_hw_mempool.c
patching file drivers/mempool/dpaa2/dpaa2_hw_mempool.h
patching file drivers/mempool/dpaa2/rte_mempool_dpaa2_version.map

Repo: dpdk-next-net
23372:
patching file MAINTAINERS
Hunk #1 FAILED at 367.
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 -7 lines).
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 succeeded at 35 with fuzz 2 (offset -7 lines).
patching file drivers/Makefile
Hunk #1 succeeded at 32 with fuzz 2 (offset -1 lines).
can't find file to patch at input line 64
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 a0725ac..1aab1cc 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
patching file drivers/mempool/dpaa2/Makefile
patching file drivers/mempool/dpaa2/dpaa2_hw_mempool.c
patching file drivers/mempool/dpaa2/dpaa2_hw_mempool.h
patching file drivers/mempool/dpaa2/rte_mempool_dpaa2_version.map

Repo: dpdk-next-virtio
23372:
patching file MAINTAINERS
Hunk #1 FAILED at 367.
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 -5 lines).
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 succeeded at 35 with fuzz 2 (offset -7 lines).
patching file drivers/Makefile
Hunk #1 succeeded at 32 with fuzz 2 (offset -1 lines).
can't find file to patch at input line 64
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 a0725ac..1aab1cc 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
patching file drivers/mempool/dpaa2/Makefile
patching file drivers/mempool/dpaa2/dpaa2_hw_mempool.c
patching file drivers/mempool/dpaa2/dpaa2_hw_mempool.h
patching file drivers/mempool/dpaa2/rte_mempool_dpaa2_version.map

Repo: dpdk-next-eventdev
23372:
patching file MAINTAINERS
Hunk #1 FAILED at 367.
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 -14 lines).
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 succeeded at 35 with fuzz 2 (offset -7 lines).
patching file drivers/Makefile
Hunk #1 succeeded at 32 with fuzz 2 (offset -1 lines).
can't find file to patch at input line 64
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 a0725ac..1aab1cc 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
patching file drivers/mempool/dpaa2/Makefile
patching file drivers/mempool/dpaa2/dpaa2_hw_mempool.c
patching file drivers/mempool/dpaa2/dpaa2_hw_mempool.h
patching file drivers/mempool/dpaa2/rte_mempool_dpaa2_version.map


DPDK STV team

                 reply	other threads:[~2017-04-11 11:56 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$11pcnnt@fmsmga001.fm.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).