From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: gaetan.rivet@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw26588 [PATCH v6 02/22] eal: fix hotplug add
Date: 07 Jul 2017 14:32:34 -0700 [thread overview]
Message-ID: <e624e2$1283bed@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/26588
_apply patch file failure_
Submitter: Gaetan Rivet <gaetan.rivet@6wind.com>
Date: Fri, 7 Jul 2017 02:09:13 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:76ee670f6a91f27eed7e06d2272db68f527c2a8b
Repo:dpdk-next-crypto, Branch:master, CommitID:324377c6f82a9274a489f3a31e1d1feef9a29aed
Repo:dpdk-next-net, Branch:master, CommitID:6cb559d67b83045e99c3c6d7de423960076ce207
Repo:dpdk-next-virtio, Branch:master, CommitID:96b1a3ad514de2a5d3fc8a12e11b9002764c1e9f
Repo:dpdk, Branch:master, CommitID:ce8af1a4398da8d2404a35fd8a5b5ab1dc05f41d
Apply patch file failed:
Repo: dpdk-next-virtio
26588:
patching file lib/librte_eal/common/eal_common_dev.c
Hunk #1 FAILED at 120.
Hunk #2 FAILED at 142.
Hunk #3 FAILED at 153.
Hunk #4 FAILED at 161.
4 out of 4 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_dev.c.rej
DPDK STV team
reply other threads:[~2017-07-07 21:32 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='e624e2$1283bed@orsmga001.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).