From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: nipun.gupta@nxp.com
Subject: [dpdk-test-report] |FAILURE| pw25342 [PATCH 20/20 v2] doc: add NXP DPAA2 EVENTDEV details
Date: 15 Jun 2017 08:38:29 -0700 [thread overview]
Message-ID: <ffb989$2v8696@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/25342
_apply patch file failure_
Submitter: Nipun Gupta <nipun.gupta@nxp.com>
Date: Thu, 15 Jun 2017 14:28:56 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:a93a816c27484017b86af9d19566218a846251f1
Repo:dpdk-next-crypto, Branch:master, CommitID:b1cac453935eb8d2f1dee8e7ab081711cfb0cf70
Repo:dpdk-next-net, Branch:master, CommitID:bc16bce5760cab9cc9115966e68e3400ca91f2bb
Repo:dpdk-next-virtio, Branch:master, CommitID:68bdd9741f40c6b948480d00a6199f3f9b834aac
Repo:dpdk, Branch:master, CommitID:98a7ea332ba3da0f74ec951595d36a616165b255
Apply patch file failed:
Repo: dpdk
25342:
patching file MAINTAINERS
Hunk #1 FAILED at 584.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file doc/guides/eventdevs/dpaa2.rst
Repo: dpdk-next-crypto
25342:
patching file MAINTAINERS
Hunk #1 FAILED at 584.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file doc/guides/eventdevs/dpaa2.rst
Repo: dpdk-next-net
25342:
patching file MAINTAINERS
Hunk #1 FAILED at 584.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file doc/guides/eventdevs/dpaa2.rst
Repo: dpdk-next-virtio
25342:
patching file MAINTAINERS
Hunk #1 FAILED at 584.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file doc/guides/eventdevs/dpaa2.rst
Repo: dpdk-next-eventdev
25342:
patching file MAINTAINERS
Hunk #1 FAILED at 584.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file doc/guides/eventdevs/dpaa2.rst
DPDK STV team
reply other threads:[~2017-06-15 15:38 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='ffb989$2v8696@orsmga002.jf.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).