From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: nipun.gupta@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw25872 [PATCH 04/21 v3] bus/fslmc: integrating dpio and dpbp to object framework
Date: 28 Jun 2017 11:17:56 -0700 [thread overview]
Message-ID: <e81775$12no74h@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2840 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/25872
_apply patch file failure_
Submitter: Nipun Gupta <nipun.gupta@nxp.com>
Date: Wed, 28 Jun 2017 20:45:47 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:c687cebe095b2ea325aa012e2834b830f1f74eba
Repo:dpdk-next-crypto, Branch:master, CommitID:41f3ff376a6dcef7c5530b390b6d9a59e4e20c55
Apply patch file failed:
Repo: dpdk
25872:
patching file drivers/bus/fslmc/fslmc_vfio.c
Hunk #1 succeeded at 363 (offset -11 lines).
Hunk #2 succeeded at 501 (offset -11 lines).
Hunk #3 succeeded at 520 (offset -11 lines).
patching file drivers/bus/fslmc/fslmc_vfio.h
Hunk #2 FAILED at 92.
1 out of 2 hunks FAILED -- saving rejects to file drivers/bus/fslmc/fslmc_vfio.h.rej
patching file drivers/bus/fslmc/portal/dpaa2_hw_dpbp.c
patching file drivers/bus/fslmc/portal/dpaa2_hw_dpio.c
Repo: dpdk-next-crypto
25872:
patching file drivers/bus/fslmc/fslmc_vfio.c
Hunk #1 succeeded at 363 (offset -11 lines).
Hunk #2 succeeded at 501 (offset -11 lines).
Hunk #3 succeeded at 520 (offset -11 lines).
patching file drivers/bus/fslmc/fslmc_vfio.h
Hunk #2 FAILED at 92.
1 out of 2 hunks FAILED -- saving rejects to file drivers/bus/fslmc/fslmc_vfio.h.rej
patching file drivers/bus/fslmc/portal/dpaa2_hw_dpbp.c
patching file drivers/bus/fslmc/portal/dpaa2_hw_dpio.c
Repo: dpdk-next-net
25872:
patching file drivers/bus/fslmc/fslmc_vfio.c
Hunk #1 succeeded at 372 (offset -2 lines).
Hunk #2 succeeded at 510 (offset -2 lines).
Hunk #3 succeeded at 529 (offset -2 lines).
patching file drivers/bus/fslmc/fslmc_vfio.h
Hunk #2 FAILED at 92.
1 out of 2 hunks FAILED -- saving rejects to file drivers/bus/fslmc/fslmc_vfio.h.rej
patching file drivers/bus/fslmc/portal/dpaa2_hw_dpbp.c
patching file drivers/bus/fslmc/portal/dpaa2_hw_dpio.c
Hunk #2 succeeded at 442 (offset -1 lines).
Repo: dpdk-next-virtio
25872:
patching file drivers/bus/fslmc/fslmc_vfio.c
Hunk #1 succeeded at 363 (offset -11 lines).
Hunk #2 succeeded at 501 (offset -11 lines).
Hunk #3 succeeded at 520 (offset -11 lines).
patching file drivers/bus/fslmc/fslmc_vfio.h
Hunk #2 FAILED at 92.
1 out of 2 hunks FAILED -- saving rejects to file drivers/bus/fslmc/fslmc_vfio.h.rej
patching file drivers/bus/fslmc/portal/dpaa2_hw_dpbp.c
patching file drivers/bus/fslmc/portal/dpaa2_hw_dpio.c
Repo: dpdk-next-eventdev
25872:
patching file drivers/bus/fslmc/fslmc_vfio.c
Hunk #1 succeeded at 363 (offset -11 lines).
Hunk #2 succeeded at 501 (offset -11 lines).
Hunk #3 succeeded at 520 (offset -11 lines).
patching file drivers/bus/fslmc/fslmc_vfio.h
Hunk #2 FAILED at 92.
1 out of 2 hunks FAILED -- saving rejects to file drivers/bus/fslmc/fslmc_vfio.h.rej
patching file drivers/bus/fslmc/portal/dpaa2_hw_dpbp.c
patching file drivers/bus/fslmc/portal/dpaa2_hw_dpio.c
DPDK STV team
reply other threads:[~2017-06-28 18:17 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$12no74h@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=nipun.gupta@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).