From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: gaetan.rivet@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw24903 [PATCH v2 10/11] ethdev: Use embedded rte_device to detach driver
Date: 01 Jun 2017 02:02:32 -0700 [thread overview]
Message-ID: <e81775$12dofnk@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3394 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/24903
_apply patch file failure_
Submitter: Gaetan Rivet <gaetan.rivet@6wind.com>
Date: Wed, 31 May 2017 15:17:55 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7021fcbb2f5a4fc3e32f2bfd1a27f3dc671d3476
Repo:dpdk-next-crypto, Branch:master, CommitID:bc6ebd8c3e7391d3d0d909a9a068caf0f2171103
Repo:dpdk-next-net, Branch:master, CommitID:a290a691a71565c0216e628fff6ddbb49a16ce8e
Repo:dpdk-next-virtio, Branch:master, CommitID:1ee9702c260bbd4a282efdeaa7277ddbfc87177a
Repo:dpdk, Branch:master, CommitID:3047c857a7edae2a2685c8cd72f15dee9d3c2b22
Apply patch file failed:
Repo: dpdk
24903:
patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
Hunk #1 FAILED at 162.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/bsdapp/eal/rte_eal_version.map.rej
patching file lib/librte_eal/common/eal_common_dev.c
Hunk #1 FAILED at 100.
Hunk #2 FAILED at 110.
Hunk #3 FAILED at 124.
3 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_dev.c.rej
patching file lib/librte_eal/common/include/rte_dev.h
patching file lib/librte_ether/rte_ethdev.c
Repo: dpdk-next-crypto
24903:
patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
Hunk #1 FAILED at 162.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/bsdapp/eal/rte_eal_version.map.rej
patching file lib/librte_eal/common/eal_common_dev.c
Hunk #1 FAILED at 100.
Hunk #2 FAILED at 110.
Hunk #3 FAILED at 124.
3 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_dev.c.rej
patching file lib/librte_eal/common/include/rte_dev.h
patching file lib/librte_ether/rte_ethdev.c
Repo: dpdk-next-net
24903:
patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
Hunk #1 FAILED at 162.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/bsdapp/eal/rte_eal_version.map.rej
patching file lib/librte_eal/common/eal_common_dev.c
Hunk #1 FAILED at 100.
Hunk #2 FAILED at 110.
Hunk #3 FAILED at 124.
3 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_dev.c.rej
patching file lib/librte_eal/common/include/rte_dev.h
patching file lib/librte_ether/rte_ethdev.c
Repo: dpdk-next-virtio
24903:
patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
Hunk #1 FAILED at 162.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/bsdapp/eal/rte_eal_version.map.rej
patching file lib/librte_eal/common/eal_common_dev.c
Hunk #1 FAILED at 100.
Hunk #2 FAILED at 110.
Hunk #3 FAILED at 124.
3 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_dev.c.rej
patching file lib/librte_eal/common/include/rte_dev.h
patching file lib/librte_ether/rte_ethdev.c
Repo: dpdk-next-eventdev
24903:
patching file lib/librte_eal/bsdapp/eal/rte_eal_version.map
Hunk #1 FAILED at 162.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/bsdapp/eal/rte_eal_version.map.rej
patching file lib/librte_eal/common/eal_common_dev.c
Hunk #1 FAILED at 100.
Hunk #2 FAILED at 110.
Hunk #3 FAILED at 124.
3 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_dev.c.rej
patching file lib/librte_eal/common/include/rte_dev.h
patching file lib/librte_ether/rte_ethdev.c
DPDK STV team
next reply other threads:[~2017-06-01 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 9:02 sys_stv [this message]
2017-06-19 3:37 sys_stv
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$12dofnk@fmsmga001.fm.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).