From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: hemant.agrawal@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw23483 [PATCH v12 01/22] net/dpaa2: introducing NXP DPAA2 PMD driver
Date: 12 Apr 2017 02:56:15 -0700 [thread overview]
Message-ID: <e81775$11pq2u0@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4815 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23483
_apply patch file failure_
Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Tue, 11 Apr 2017 19:19:30 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:41c63e15eb931fee8e52e36570cab79a9817b960
Repo:dpdk-next-net, Branch:master, CommitID:f2aca14e69c739de6f5ae3d558c9c62bb5dd026f
Apply patch file failed:
Repo: dpdk
23483:
patching file MAINTAINERS
Hunk #1 FAILED at 374.
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 -8 lines).
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 54.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
patching file drivers/Makefile
Hunk #1 succeeded at 33 with fuzz 2 (offset -2 lines).
patching file drivers/net/Makefile
Hunk #1 succeeded at 49 (offset -2 lines).
patching file drivers/net/dpaa2/Makefile
patching file drivers/net/dpaa2/dpaa2_ethdev.c
patching file drivers/net/dpaa2/dpaa2_ethdev.h
patching file drivers/net/dpaa2/rte_pmd_dpaa2_version.map
patching file mk/rte.app.mk
Hunk #1 succeeded at 113 (offset -1 lines).
Hunk #2 succeeded at 166 (offset -1 lines).
Repo: dpdk-next-crypto
23483:
patching file MAINTAINERS
Hunk #1 FAILED at 374.
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 -8 lines).
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 54.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
patching file drivers/Makefile
Hunk #1 succeeded at 33 with fuzz 2 (offset -2 lines).
patching file drivers/net/Makefile
Hunk #1 succeeded at 49 (offset -2 lines).
patching file drivers/net/dpaa2/Makefile
patching file drivers/net/dpaa2/dpaa2_ethdev.c
patching file drivers/net/dpaa2/dpaa2_ethdev.h
patching file drivers/net/dpaa2/rte_pmd_dpaa2_version.map
patching file mk/rte.app.mk
Hunk #1 succeeded at 113 (offset -1 lines).
Hunk #2 succeeded at 166 (offset -1 lines).
Repo: dpdk-next-net
23483:
patching file MAINTAINERS
Hunk #1 FAILED at 374.
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 -10 lines).
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 54.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
patching file drivers/Makefile
Hunk #1 succeeded at 33 with fuzz 2 (offset -2 lines).
patching file drivers/net/Makefile
patching file drivers/net/dpaa2/Makefile
patching file drivers/net/dpaa2/dpaa2_ethdev.c
patching file drivers/net/dpaa2/dpaa2_ethdev.h
patching file drivers/net/dpaa2/rte_pmd_dpaa2_version.map
patching file mk/rte.app.mk
Repo: dpdk-next-virtio
23483:
patching file MAINTAINERS
Hunk #1 FAILED at 374.
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 -8 lines).
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 54.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
patching file drivers/Makefile
Hunk #1 succeeded at 33 with fuzz 2 (offset -2 lines).
patching file drivers/net/Makefile
Hunk #1 succeeded at 44 (offset -7 lines).
patching file drivers/net/dpaa2/Makefile
patching file drivers/net/dpaa2/dpaa2_ethdev.c
patching file drivers/net/dpaa2/dpaa2_ethdev.h
patching file drivers/net/dpaa2/rte_pmd_dpaa2_version.map
patching file mk/rte.app.mk
Hunk #1 succeeded at 113 (offset -1 lines).
Hunk #2 succeeded at 166 (offset -1 lines).
Repo: dpdk-next-eventdev
23483:
patching file MAINTAINERS
Hunk #1 FAILED at 374.
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 -17 lines).
patching file config/defconfig_arm64-dpaa2-linuxapp-gcc
Hunk #1 FAILED at 54.
1 out of 1 hunk FAILED -- saving rejects to file config/defconfig_arm64-dpaa2-linuxapp-gcc.rej
patching file drivers/Makefile
Hunk #1 succeeded at 33 with fuzz 2 (offset -2 lines).
patching file drivers/net/Makefile
Hunk #1 succeeded at 42 (offset -9 lines).
patching file drivers/net/dpaa2/Makefile
patching file drivers/net/dpaa2/dpaa2_ethdev.c
patching file drivers/net/dpaa2/dpaa2_ethdev.h
patching file drivers/net/dpaa2/rte_pmd_dpaa2_version.map
patching file mk/rte.app.mk
Hunk #1 succeeded at 110 (offset -4 lines).
Hunk #2 succeeded at 159 (offset -8 lines).
DPDK STV team
reply other threads:[~2017-04-12 9: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$11pq2u0@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).