From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: shreyansh.jain@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw39125 [PATCH 3/3] bus/dpaa: optimize physical to virtual address searching
Date: 09 May 2018 23:01:09 -0700 [thread overview]
Message-ID: <0590c7$1k4fgh@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2771 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/39125
_apply patch file failure_
Submitter: Shreyansh Jain <shreyansh.jain@nxp.com>
Date: Fri, 27 Apr 2018 21:55:54 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:640b0d1e510e111694c25145466f37867453837f
Repo:dpdk-next-crypto, Branch:master, CommitID:728ca9b0d5abea82cd01dee6645456a9d56215f7
Repo:dpdk-next-net, Branch:master, CommitID:774c1892c434dba09998ccc76b956feb72224571
Repo:dpdk-next-virtio, Branch:master, CommitID:037c0996bc927342f157426739e0cb63f2db8689
Repo:dpdk, Branch:master, CommitID:8ea41438832a360aed2b7ba49fb75e310a2ff1dc
Apply patch file failed:
Repo: dpdk
39125:
patching file drivers/bus/dpaa/rte_dpaa_bus.h
Hunk #1 FAILED at 95.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/dpaa/rte_dpaa_bus.h.rej
patching file drivers/mempool/dpaa/dpaa_mempool.c
Hunk #1 succeeded at 34 with fuzz 2 (offset 7 lines).
Hunk #2 FAILED at 294.
1 out of 2 hunks FAILED -- saving rejects to file drivers/mempool/dpaa/dpaa_mempool.c.rej
Repo: dpdk-next-crypto
39125:
patching file drivers/bus/dpaa/rte_dpaa_bus.h
Hunk #1 FAILED at 95.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/dpaa/rte_dpaa_bus.h.rej
patching file drivers/mempool/dpaa/dpaa_mempool.c
Hunk #1 succeeded at 34 with fuzz 2 (offset 7 lines).
Hunk #2 FAILED at 294.
1 out of 2 hunks FAILED -- saving rejects to file drivers/mempool/dpaa/dpaa_mempool.c.rej
Repo: dpdk-next-net
39125:
patching file drivers/bus/dpaa/rte_dpaa_bus.h
Hunk #1 FAILED at 95.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/dpaa/rte_dpaa_bus.h.rej
patching file drivers/mempool/dpaa/dpaa_mempool.c
Hunk #1 succeeded at 34 with fuzz 2 (offset 7 lines).
Hunk #2 FAILED at 294.
1 out of 2 hunks FAILED -- saving rejects to file drivers/mempool/dpaa/dpaa_mempool.c.rej
Repo: dpdk-next-virtio
39125:
patching file drivers/bus/dpaa/rte_dpaa_bus.h
Hunk #1 FAILED at 95.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/dpaa/rte_dpaa_bus.h.rej
patching file drivers/mempool/dpaa/dpaa_mempool.c
Hunk #1 succeeded at 34 with fuzz 2 (offset 7 lines).
Hunk #2 FAILED at 294.
1 out of 2 hunks FAILED -- saving rejects to file drivers/mempool/dpaa/dpaa_mempool.c.rej
Repo: dpdk-next-eventdev
39125:
patching file drivers/bus/dpaa/rte_dpaa_bus.h
Hunk #1 FAILED at 95.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/dpaa/rte_dpaa_bus.h.rej
patching file drivers/mempool/dpaa/dpaa_mempool.c
Hunk #1 succeeded at 34 with fuzz 2 (offset 7 lines).
Hunk #2 FAILED at 294.
1 out of 2 hunks FAILED -- saving rejects to file drivers/mempool/dpaa/dpaa_mempool.c.rej
DPDK STV team
reply other threads:[~2018-05-10 6:01 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='0590c7$1k4fgh@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=shreyansh.jain@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).