From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: gaetan.rivet@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw38029 [PATCH v6 10/22] eal/dev: implement device iteration initialization
Date: 25 Apr 2018 13:45:18 -0700 [thread overview]
Message-ID: <f7a79a$1j5amp@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3249 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38029
_apply patch file failure_
Submitter: Gaetan Rivet <gaetan.rivet@6wind.com>
Date: Fri, 13 Apr 2018 15:22:28 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
Repo:dpdk-next-crypto, Branch:master, CommitID:eb8a86e275ef15a5455948d679d1a2c43dd4c740
Repo:dpdk-next-net, Branch:master, CommitID:8ed3fbfd59bbd05dcb6524ef2b1dbde43d41f1e3
Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
Repo:dpdk, Branch:master, CommitID:13573bd3f431934da373b1332ef92f8c30940272
Apply patch file failed:
Repo: dpdk
38029:
patching file lib/Makefile
Hunk #1 succeeded at 5 with fuzz 2 (offset -1 lines).
patching file lib/librte_eal/bsdapp/eal/Makefile
patching file lib/librte_eal/common/eal_common_dev.c
Hunk #2 succeeded at 346 (offset -25 lines).
patching file lib/librte_eal/common/include/rte_dev.h
patching file lib/librte_eal/linuxapp/eal/Makefile
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 223.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej
Repo: dpdk-next-crypto
38029:
patching file lib/Makefile
Hunk #1 succeeded at 5 with fuzz 2 (offset -1 lines).
patching file lib/librte_eal/bsdapp/eal/Makefile
patching file lib/librte_eal/common/eal_common_dev.c
patching file lib/librte_eal/common/include/rte_dev.h
patching file lib/librte_eal/linuxapp/eal/Makefile
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 223.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej
Repo: dpdk-next-net
38029:
patching file lib/Makefile
Hunk #1 succeeded at 5 with fuzz 2 (offset -1 lines).
patching file lib/librte_eal/bsdapp/eal/Makefile
patching file lib/librte_eal/common/eal_common_dev.c
Hunk #2 succeeded at 346 (offset -25 lines).
patching file lib/librte_eal/common/include/rte_dev.h
patching file lib/librte_eal/linuxapp/eal/Makefile
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 223.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej
Repo: dpdk-next-virtio
38029:
patching file lib/Makefile
Hunk #1 succeeded at 5 with fuzz 2 (offset -1 lines).
patching file lib/librte_eal/bsdapp/eal/Makefile
patching file lib/librte_eal/common/eal_common_dev.c
patching file lib/librte_eal/common/include/rte_dev.h
patching file lib/librte_eal/linuxapp/eal/Makefile
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 223.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej
Repo: dpdk-next-eventdev
38029:
patching file lib/Makefile
Hunk #1 succeeded at 5 with fuzz 2 (offset -1 lines).
patching file lib/librte_eal/bsdapp/eal/Makefile
patching file lib/librte_eal/common/eal_common_dev.c
patching file lib/librte_eal/common/include/rte_dev.h
patching file lib/librte_eal/linuxapp/eal/Makefile
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 223.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej
DPDK STV team
reply other threads:[~2018-04-25 20:45 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$1j5amp@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=gaetan.rivet@6wind.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).