From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: gaetan.rivet@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw25148 [PATCH v3 1/3] pci: implement hotplug bus operation
Date: 08 Jun 2017 10:26:16 -0700 [thread overview]
Message-ID: <63cbe6$135baa8@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1807 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/25148
_apply patch file failure_
Submitter: Gaetan Rivet <gaetan.rivet@6wind.com>
Date: Thu, 8 Jun 2017 01:58:28 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:a93a816c27484017b86af9d19566218a846251f1
Repo:dpdk-next-crypto, Branch:master, CommitID:42fec1bba0af092ddedc5c71d3e873274621bc5d
Repo:dpdk-next-net, Branch:master, CommitID:cc9b164786c61feb814f32d799393656815a3305
Repo:dpdk-next-virtio, Branch:master, CommitID:101a00a4811479e7f66829e523c9138288831b39
Repo:dpdk, Branch:master, CommitID:c6dfeecb1581103c2a6cd95c8158e8bff18b9667
Apply patch file failed:
Repo: dpdk
25148:
patching file lib/librte_eal/common/eal_common_pci.c
Hunk #2 FAILED at 518.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_pci.c.rej
Repo: dpdk-next-crypto
25148:
patching file lib/librte_eal/common/eal_common_pci.c
Hunk #2 FAILED at 518.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_pci.c.rej
Repo: dpdk-next-net
25148:
patching file lib/librte_eal/common/eal_common_pci.c
Hunk #2 FAILED at 518.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_pci.c.rej
Repo: dpdk-next-virtio
25148:
patching file lib/librte_eal/common/eal_common_pci.c
Hunk #1 succeeded at 76 (offset 29 lines).
Hunk #2 FAILED at 518.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_pci.c.rej
Repo: dpdk-next-eventdev
25148:
patching file lib/librte_eal/common/eal_common_pci.c
Hunk #2 FAILED at 518.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_pci.c.rej
DPDK STV team
reply other threads:[~2017-06-08 17:26 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$135baa8@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).