From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: gaetan.rivet@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw26952 [PATCH v4 8/8] bus: remove useless plug parameter
Date: 15 Jul 2017 12:00:55 -0700 [thread overview]
Message-ID: <e81775$12uk5e8@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3513 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/26952
_apply patch file failure_
Submitter: Gaetan Rivet <gaetan.rivet@6wind.com>
Date: Sat, 15 Jul 2017 19:56:42 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:76ee670f6a91f27eed7e06d2272db68f527c2a8b
Repo:dpdk-next-crypto, Branch:master, CommitID:bc9759d9a12adc488fe401087da8fbb79f99789b
Repo:dpdk-next-net, Branch:master, CommitID:b3d4e665ed3db9fb21ba016a28294245d578e012
Repo:dpdk-next-virtio, Branch:master, CommitID:23079506d3566585c9b3bde703ddf5db81d50186
Repo:dpdk, Branch:master, CommitID:645bd25ad8f905fcdf06b9c319228af03ff8708e
Apply patch file failed:
Repo: dpdk
26952:
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 522 with fuzz 2 (offset -19 lines).
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 FAILED at 319.
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
26952:
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 522 with fuzz 2 (offset -19 lines).
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 FAILED at 319.
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
26952:
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 507 with fuzz 2 (offset -34 lines).
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 FAILED at 319.
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
26952:
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 522 with fuzz 2 (offset -19 lines).
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 FAILED at 319.
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-eventdev
26952:
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 507 with fuzz 2 (offset -34 lines).
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 FAILED at 319.
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-15 19:00 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='e81775$12uk5e8@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).