From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: gaetan.rivet@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw26844 [PATCH v3 8/8] bus: remove useless plug parameter
Date: 11 Jul 2017 18:35:51 -0700 [thread overview]
Message-ID: <63cbe6$13itsiq@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3555 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/26844
_apply patch file failure_
Submitter: Gaetan Rivet <gaetan.rivet@6wind.com>
Date: Wed, 12 Jul 2017 01:25:36 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:76ee670f6a91f27eed7e06d2272db68f527c2a8b
Repo:dpdk-next-crypto, Branch:master, CommitID:70ef8b3f3a0857f3c3cfbe71c24fde42c8276aff
Repo:dpdk-next-net, Branch:master, CommitID:b3d4e665ed3db9fb21ba016a28294245d578e012
Repo:dpdk-next-virtio, Branch:master, CommitID:42003749105c3bbd7a9e2664263d89e502665cbe
Repo:dpdk, Branch:master, CommitID:441ea8899e9e4c253737f316891815b07df4c83f
Apply patch file failed:
Repo: dpdk
26844:
patching file lib/librte_eal/common/eal_common_dev.c
Hunk #1 FAILED at 188.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/eal_common_dev.c.rej
patching file lib/librte_eal/common/eal_common_pci.c
Hunk #1 succeeded at 523 with fuzz 2 (offset -18 lines).
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 FAILED at 316.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/eal_common_vdev.c.rej
patching file lib/librte_eal/common/include/rte_bus.h
Repo: dpdk-next-crypto
26844:
patching file lib/librte_eal/common/eal_common_dev.c
Hunk #1 FAILED at 188.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/eal_common_dev.c.rej
patching file lib/librte_eal/common/eal_common_pci.c
Hunk #1 succeeded at 523 with fuzz 2 (offset -18 lines).
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 FAILED at 316.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/eal_common_vdev.c.rej
patching file lib/librte_eal/common/include/rte_bus.h
Repo: dpdk-next-net
26844:
patching file lib/librte_eal/common/eal_common_dev.c
Hunk #1 FAILED at 188.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/eal_common_dev.c.rej
patching file lib/librte_eal/common/eal_common_pci.c
Hunk #1 succeeded at 508 with fuzz 2 (offset -33 lines).
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 FAILED at 316.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/eal_common_vdev.c.rej
patching file lib/librte_eal/common/include/rte_bus.h
Hunk #1 succeeded at 114 (offset 1 line).
Repo: dpdk-next-virtio
26844:
patching file lib/librte_eal/common/eal_common_dev.c
Hunk #1 FAILED at 188.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/eal_common_dev.c.rej
patching file lib/librte_eal/common/eal_common_pci.c
Hunk #1 succeeded at 508 with fuzz 2 (offset -33 lines).
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 FAILED at 316.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/eal_common_vdev.c.rej
patching file lib/librte_eal/common/include/rte_bus.h
Hunk #1 succeeded at 114 (offset 1 line).
Repo: dpdk-next-eventdev
26844:
patching file lib/librte_eal/common/eal_common_dev.c
Hunk #1 FAILED at 188.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/eal_common_dev.c.rej
patching file lib/librte_eal/common/eal_common_pci.c
Hunk #1 succeeded at 508 with fuzz 2 (offset -33 lines).
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 FAILED at 316.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/eal_common_vdev.c.rej
patching file lib/librte_eal/common/include/rte_bus.h
Hunk #1 succeeded at 114 (offset 1 line).
DPDK STV team
reply other threads:[~2017-07-12 1:35 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='63cbe6$13itsiq@fmsmga002.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).