From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: yuanhan.liu@linux.intel.com
Subject: [dpdk-test-report] |FAILURE| pw19160 [PATCH 2/2] net/virtio: do not store PCI device pointer at shared memory
Date: 12 Jan 2017 03:14:51 -0800 [thread overview]
Message-ID: <63cbe6$11418ri@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]
Test-Label: Intel compilation
Test-Status: FAILURE
http://dpdk.org/patch/19160
_apply patch file failure_
Submitter: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Date: Thu, 12 Jan 2017 14:03:20 +0800
DPDK git baseline: Repo:dpdk-next-crypto, Branch:master, CommitID:afe425f602a8bea436b83d664025a95d69b722ae
Repo:dpdk-next-net, Branch:master, CommitID:aaa9bebd57d51c5529201445ab1ac26a6656ce46
Repo:dpdk-next-virtio, Branch:master, CommitID:2b2669fc4c792f9a3ab73490bb93f7810a71c089
Repo:dpdk, Branch:master, CommitID:6de5c0f1302cc9e310a47e3488d7d3f1a4602b64
Apply patch file failed:
Repo: dpdk-next-net
19160:
patching file drivers/net/virtio/virtio_ethdev.c
Hunk #1 succeeded at 488 (offset -1 lines).
Hunk #2 succeeded at 1193 (offset -1 lines).
Hunk #3 FAILED at 1214.
Hunk #4 succeeded at 1350 (offset -56 lines).
Hunk #5 succeeded at 1370 (offset -56 lines).
Hunk #6 succeeded at 1629 (offset -56 lines).
1 out of 6 hunks FAILED -- saving rejects to file drivers/net/virtio/virtio_ethdev.c.rej
patching file drivers/net/virtio/virtio_pci.c
Hunk #1 succeeded at 727 (offset -3 lines).
patching file drivers/net/virtio/virtio_pci.h
Hunk #1 succeeded at 258 with fuzz 1.
Repo: dpdk-next-virtio
19160:
patching file drivers/net/virtio/virtio_ethdev.c
Hunk #1 FAILED at 489.
Hunk #2 FAILED at 1194.
Hunk #3 FAILED at 1214.
Hunk #4 FAILED at 1406.
Hunk #5 FAILED at 1428.
Hunk #6 FAILED at 1687.
6 out of 6 hunks FAILED -- saving rejects to file drivers/net/virtio/virtio_ethdev.c.rej
patching file drivers/net/virtio/virtio_pci.c
Hunk #1 succeeded at 727 (offset -3 lines).
patching file drivers/net/virtio/virtio_pci.h
Hunk #1 succeeded at 258 with fuzz 1.
DPDK STV team
reply other threads:[~2017-01-12 11:14 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$11418ri@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=yuanhan.liu@linux.intel.com \
/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).