From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: matan@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw34176 [PATCH v4 6/7] net/failsafe: use ownership mechanism to own ports
Date: 22 Jan 2018 08:51:52 -0800 [thread overview]
Message-ID: <0590c7$o6b77@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/34176
_apply patch file failure_
Submitter: Matan Azrad <matan@mellanox.com>
Date: Sat, 20 Jan 2018 21:24:25 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:18daa7305ffd89b443cf56694fd30790cca0d3ce
Repo:dpdk-next-crypto, Branch:master, CommitID:d3091b0f880e35ca8d5fb4f8385de055bb7f450d
Repo:dpdk-next-net, Branch:master, CommitID:bf375b4d51170cd58ca50c646781cb6de17766ea
Repo:dpdk-next-virtio, Branch:master, CommitID:dd854ceec2e09a93f2509de03ae6d67e201b1a2b
Repo:dpdk, Branch:master, CommitID:bf375b4d51170cd58ca50c646781cb6de17766ea
Apply patch file failed:
Repo: dpdk-next-virtio
34176:
patching file drivers/net/failsafe/failsafe.c
patching file drivers/net/failsafe/failsafe_eal.c
Hunk #1 FAILED at 106.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/failsafe/failsafe_eal.c.rej
patching file drivers/net/failsafe/failsafe_private.h
Hunk #2 succeeded at 141 (offset -5 lines).
Repo: dpdk-next-eventdev
34176:
patching file drivers/net/failsafe/failsafe.c
patching file drivers/net/failsafe/failsafe_eal.c
Hunk #1 FAILED at 106.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/failsafe/failsafe_eal.c.rej
patching file drivers/net/failsafe/failsafe_private.h
Hunk #2 succeeded at 141 (offset -5 lines).
DPDK STV team
reply other threads:[~2018-01-22 16:52 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='0590c7$o6b77@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=matan@mellanox.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).