From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xinfengx.zhao@intel.com, zhaoyan.chen@intel.com, peipeix.lu@intel.com
Subject: [dpdk-test-report] |FAILURE| pw39254[dpdk-dev, v4, 1/7] mempool/dpaa2: add functions exposed to DPDK applications
Date: 02 May 2018 10:22:38 -0700 [thread overview]
Message-ID: <0590c7$1i69up@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4173 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/39254
_apply issues_
Submitter: Nipun Gupta <nipun.gupta@nxp.com>
Date: 2018-05-02 17:15:23
DPDK git baseline:
Repo:dpdk-master, CommitID: 0db6d2782cfabb8ceb10052897e30ac084010894
Repo:dpdk-next-eventdev, CommitID: fcde84b5f85b3c1a5d5564299fd49c58ca20370d
Repo:dpdk-next-net, CommitID: 9a16e2c6b5586ab0ff453ed1d037efe7bdb9a4ff
Repo:dpdk-next-crypto, CommitID: 211992f3b7df5d6d8f1dbefc48bc37a6d5398fbc
Repo:dpdk-next-virtio, CommitID: 81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
*Repo: dpdk-master
Checking patch doc/api/doxy-api-index.md...
error: while searching for:
[i40e] (@ref rte_pmd_i40e.h),
[bnxt] (@ref rte_pmd_bnxt.h),
[dpaa] (@ref rte_pmd_dpaa.h),
[dpaa2_qdma] (@ref rte_pmd_dpaa2_qdma.h),
[crypto_scheduler] (@ref rte_cryptodev_scheduler.h)
error: patch failed: doc/api/doxy-api-index.md:38
error: doc/api/doxy-api-index.md: patch does not apply
Checking patch doc/api/doxy-api.conf...
Checking patch drivers/mempool/dpaa2/Makefile...
Checking patch drivers/mempool/dpaa2/dpaa2_hw_mempool.c...
Checking patch drivers/mempool/dpaa2/rte_dpaa2_mempool.h...
Checking patch drivers/mempool/dpaa2/rte_mempool_dpaa2_version.map...
*Repo: dpdk-next-eventdev
Checking patch doc/api/doxy-api-index.md...
error: while searching for:
[i40e] (@ref rte_pmd_i40e.h),
[bnxt] (@ref rte_pmd_bnxt.h),
[dpaa] (@ref rte_pmd_dpaa.h),
[dpaa2_qdma] (@ref rte_pmd_dpaa2_qdma.h),
[crypto_scheduler] (@ref rte_cryptodev_scheduler.h)
error: patch failed: doc/api/doxy-api-index.md:38
error: doc/api/doxy-api-index.md: patch does not apply
Checking patch doc/api/doxy-api.conf...
Checking patch drivers/mempool/dpaa2/Makefile...
Checking patch drivers/mempool/dpaa2/dpaa2_hw_mempool.c...
Checking patch drivers/mempool/dpaa2/rte_dpaa2_mempool.h...
Checking patch drivers/mempool/dpaa2/rte_mempool_dpaa2_version.map...
*Repo: dpdk-next-net
Checking patch doc/api/doxy-api-index.md...
error: while searching for:
[i40e] (@ref rte_pmd_i40e.h),
[bnxt] (@ref rte_pmd_bnxt.h),
[dpaa] (@ref rte_pmd_dpaa.h),
[dpaa2_qdma] (@ref rte_pmd_dpaa2_qdma.h),
[crypto_scheduler] (@ref rte_cryptodev_scheduler.h)
error: patch failed: doc/api/doxy-api-index.md:38
error: doc/api/doxy-api-index.md: patch does not apply
Checking patch doc/api/doxy-api.conf...
Checking patch drivers/mempool/dpaa2/Makefile...
Checking patch drivers/mempool/dpaa2/dpaa2_hw_mempool.c...
Checking patch drivers/mempool/dpaa2/rte_dpaa2_mempool.h...
Checking patch drivers/mempool/dpaa2/rte_mempool_dpaa2_version.map...
*Repo: dpdk-next-crypto
Checking patch doc/api/doxy-api-index.md...
error: while searching for:
[i40e] (@ref rte_pmd_i40e.h),
[bnxt] (@ref rte_pmd_bnxt.h),
[dpaa] (@ref rte_pmd_dpaa.h),
[dpaa2_qdma] (@ref rte_pmd_dpaa2_qdma.h),
[crypto_scheduler] (@ref rte_cryptodev_scheduler.h)
error: patch failed: doc/api/doxy-api-index.md:38
error: doc/api/doxy-api-index.md: patch does not apply
Checking patch doc/api/doxy-api.conf...
Checking patch drivers/mempool/dpaa2/Makefile...
Checking patch drivers/mempool/dpaa2/dpaa2_hw_mempool.c...
Checking patch drivers/mempool/dpaa2/rte_dpaa2_mempool.h...
Checking patch drivers/mempool/dpaa2/rte_mempool_dpaa2_version.map...
*Repo: dpdk-next-virtio
Checking patch doc/api/doxy-api-index.md...
error: while searching for:
[i40e] (@ref rte_pmd_i40e.h),
[bnxt] (@ref rte_pmd_bnxt.h),
[dpaa] (@ref rte_pmd_dpaa.h),
[dpaa2_qdma] (@ref rte_pmd_dpaa2_qdma.h),
[crypto_scheduler] (@ref rte_cryptodev_scheduler.h)
error: patch failed: doc/api/doxy-api-index.md:38
error: doc/api/doxy-api-index.md: patch does not apply
Checking patch doc/api/doxy-api.conf...
Checking patch drivers/mempool/dpaa2/Makefile...
Checking patch drivers/mempool/dpaa2/dpaa2_hw_mempool.c...
Hunk #2 succeeded at 238 (offset -7 lines).
Checking patch drivers/mempool/dpaa2/rte_dpaa2_mempool.h...
DPDK STV team
reply other threads:[~2018-05-02 17:22 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$1i69up@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=peipeix.lu@intel.com \
--cc=test-report@dpdk.org \
--cc=xinfengx.zhao@intel.com \
--cc=zhaoyan.chen@intel.com \
/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).