From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: hemant.agrawal@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw33422 [PATCH v3 13/19] bus/dpaa: query queue frame count support
Date: 16 Jan 2018 16:36:38 -0800 [thread overview]
Message-ID: <f7a79a$pp0kt@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3026 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/33422
_apply patch file failure_
Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Wed, 10 Jan 2018 16:16:41 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:49194debd126076ab0805f608340017af2df8655
Repo:dpdk-next-crypto, Branch:master, CommitID:2644d66b2bcc62abb58cdce8121f204962d083b8
Repo:dpdk-next-net, Branch:master, CommitID:0f708db31ed0a8616165f90c4abbb9c0382df5eb
Repo:dpdk-next-virtio, Branch:master, CommitID:9158926a0f24e9b8cccfe97211fa72d52a6f6a36
Repo:dpdk, Branch:master, CommitID:5329b95aae3a22aaadc6888ae17c7082996abb97
Apply patch file failed:
Repo: dpdk
33422:
patching file drivers/bus/dpaa/base/qbman/qman.c
Hunk #1 succeeded at 1808 (offset 86 lines).
patching file drivers/bus/dpaa/include/fsl_qman.h
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/bus/dpaa/include/fsl_qman.h.rej
patching file drivers/bus/dpaa/rte_bus_dpaa_version.map
Hunk #1 FAILED at 73.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/dpaa/rte_bus_dpaa_version.map.rej
Repo: dpdk-next-crypto
33422:
patching file drivers/bus/dpaa/base/qbman/qman.c
Hunk #1 succeeded at 1666 (offset -56 lines).
patching file drivers/bus/dpaa/include/fsl_qman.h
Hunk #1 succeeded at 1611 (offset -5 lines).
patching file drivers/bus/dpaa/rte_bus_dpaa_version.map
Hunk #1 FAILED at 73.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/dpaa/rte_bus_dpaa_version.map.rej
Repo: dpdk-next-net
33422:
patching file drivers/bus/dpaa/base/qbman/qman.c
Hunk #1 succeeded at 1808 (offset 86 lines).
patching file drivers/bus/dpaa/include/fsl_qman.h
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/bus/dpaa/include/fsl_qman.h.rej
patching file drivers/bus/dpaa/rte_bus_dpaa_version.map
Hunk #1 FAILED at 73.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/dpaa/rte_bus_dpaa_version.map.rej
Repo: dpdk-next-virtio
33422:
patching file drivers/bus/dpaa/base/qbman/qman.c
Hunk #1 succeeded at 1666 (offset -56 lines).
patching file drivers/bus/dpaa/include/fsl_qman.h
Hunk #1 succeeded at 1611 (offset -5 lines).
patching file drivers/bus/dpaa/rte_bus_dpaa_version.map
Hunk #1 FAILED at 73.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/dpaa/rte_bus_dpaa_version.map.rej
Repo: dpdk-next-eventdev
33422:
patching file drivers/bus/dpaa/base/qbman/qman.c
Hunk #1 succeeded at 1666 (offset -56 lines).
patching file drivers/bus/dpaa/include/fsl_qman.h
Hunk #1 succeeded at 1611 (offset -5 lines).
patching file drivers/bus/dpaa/rte_bus_dpaa_version.map
Hunk #1 FAILED at 73.
1 out of 1 hunk FAILED -- saving rejects to file drivers/bus/dpaa/rte_bus_dpaa_version.map.rej
DPDK STV team
reply other threads:[~2018-01-17 0:36 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='f7a79a$pp0kt@orsmga002.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).