From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: hemant.agrawal@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw28784 [PATCH v3 14/27] net/dpaa2: add support for link status event
Date: 20 Sep 2017 03:53:04 -0700 [thread overview]
Message-ID: <7327ef$432pq7@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3791 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/28784
_apply patch file failure_
Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Sat, 16 Sep 2017 16:22:37 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:430b815c50d458c7207ce11d36aabf0184c86f79
Repo:dpdk-next-crypto, Branch:master, CommitID:176c6bcf3250fce8b054618df942acbf4add6d80
Repo:dpdk-next-net, Branch:master, CommitID:05c965e11608f602c7224259d4373416e2eb50d5
Repo:dpdk-next-virtio, Branch:master, CommitID:fee08fe0d67d46639d25c201738d9b1b867e443c
Repo:dpdk, Branch:master, CommitID:3d2e0448ebb5c76fda6e988558793c070c3baded
Apply patch file failed:
Repo: dpdk
28784:
patching file doc/guides/nics/features/dpaa2.ini
patching file drivers/net/dpaa2/dpaa2_ethdev.c
Hunk #7 succeeded at 1583 (offset 3 lines).
patching file drivers/net/dpaa2/mc/dpni.c
Hunk #1 FAILED at 351.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/dpaa2/mc/dpni.c.rej
patching file drivers/net/dpaa2/mc/fsl_dpni.h
Hunk #1 succeeded at 354 with fuzz 1 (offset 107 lines).
patching file drivers/net/dpaa2/mc/fsl_dpni_cmd.h
Hunk #1 FAILED at 64.
Hunk #2 FAILED at 169.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/dpaa2/mc/fsl_dpni_cmd.h.rej
Repo: dpdk-next-crypto
28784:
patching file doc/guides/nics/features/dpaa2.ini
patching file drivers/net/dpaa2/dpaa2_ethdev.c
Hunk #7 succeeded at 1583 (offset 3 lines).
patching file drivers/net/dpaa2/mc/dpni.c
Hunk #1 FAILED at 351.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/dpaa2/mc/dpni.c.rej
patching file drivers/net/dpaa2/mc/fsl_dpni.h
Hunk #1 succeeded at 354 with fuzz 1 (offset 107 lines).
patching file drivers/net/dpaa2/mc/fsl_dpni_cmd.h
Hunk #1 FAILED at 64.
Hunk #2 FAILED at 169.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/dpaa2/mc/fsl_dpni_cmd.h.rej
Repo: dpdk-next-net
28784:
patching file doc/guides/nics/features/dpaa2.ini
patching file drivers/net/dpaa2/dpaa2_ethdev.c
Hunk #7 succeeded at 1583 (offset 3 lines).
patching file drivers/net/dpaa2/mc/dpni.c
Hunk #1 FAILED at 351.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/dpaa2/mc/dpni.c.rej
patching file drivers/net/dpaa2/mc/fsl_dpni.h
Hunk #1 succeeded at 354 with fuzz 1 (offset 107 lines).
patching file drivers/net/dpaa2/mc/fsl_dpni_cmd.h
Hunk #1 FAILED at 64.
Hunk #2 FAILED at 169.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/dpaa2/mc/fsl_dpni_cmd.h.rej
Repo: dpdk-next-virtio
28784:
patching file doc/guides/nics/features/dpaa2.ini
patching file drivers/net/dpaa2/dpaa2_ethdev.c
Hunk #7 succeeded at 1583 (offset 3 lines).
patching file drivers/net/dpaa2/mc/dpni.c
Hunk #1 FAILED at 351.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/dpaa2/mc/dpni.c.rej
patching file drivers/net/dpaa2/mc/fsl_dpni.h
Hunk #1 succeeded at 354 with fuzz 1 (offset 107 lines).
patching file drivers/net/dpaa2/mc/fsl_dpni_cmd.h
Hunk #1 FAILED at 64.
Hunk #2 FAILED at 169.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/dpaa2/mc/fsl_dpni_cmd.h.rej
Repo: dpdk-next-eventdev
28784:
patching file doc/guides/nics/features/dpaa2.ini
patching file drivers/net/dpaa2/dpaa2_ethdev.c
Hunk #7 succeeded at 1583 (offset 3 lines).
patching file drivers/net/dpaa2/mc/dpni.c
Hunk #1 FAILED at 351.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/dpaa2/mc/dpni.c.rej
patching file drivers/net/dpaa2/mc/fsl_dpni.h
Hunk #1 succeeded at 354 with fuzz 1 (offset 107 lines).
patching file drivers/net/dpaa2/mc/fsl_dpni_cmd.h
Hunk #1 FAILED at 64.
Hunk #2 FAILED at 169.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/dpaa2/mc/fsl_dpni_cmd.h.rej
DPDK STV team
reply other threads:[~2017-09-20 10:53 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='7327ef$432pq7@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).