From: sys_stv@intel.com
To: jianfeng.tan@intel.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw13488-13493 virtio: hide phys addr check inside pci ops
Date: 13 Jun 2016 01:40:45 -0700 [thread overview]
Message-ID: <9c8bee$tci26q@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1647 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork ID: 13488-13493
http://www.dpdk.org/dev/patchwork/patch/13493/
Submitter: Jianfeng Tan <jianfeng.tan@intel.com>
Date: Mon, 13 Jun 2016 06:38:58 +0000
DPDK git baseline: dd9ae4c7b302dffd9b3dac849f4da8badac91719
Check patch:Success
patch file error:
13488:
patching file drivers/net/virtio/virtio_ethdev.c
Reversed (or previously applied) patch detected! Assume -R? [n] Apply anyway? [n] Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file drivers/net/virtio/virtio_ethdev.c.rej
patching file drivers/net/virtio/virtio_pci.c Hunk #2 FAILED at 159.
Hunk #3 FAILED at 383.
2 out of 4 hunks FAILED -- saving rejects to file drivers/net/virtio/virtio_pci.c.rej
patching file drivers/net/virtio/virtio_pci.h Hunk #1 succeeded at 234 (offset -1 lines).
13489:
patching file drivers/net/virtio/virtio_ethdev.c
Hunk #1 FAILED at 431.
Hunk #2 succeeded at 410 with fuzz 2 (offset -32 lines).
Hunk #3 FAILED at 487.
2 out of 3 hunks FAILED -- saving rejects to file drivers/net/virtio/virtio_ethdev.c.rej
patching file drivers/net/virtio/virtio_rxtx.c Hunk #2 succeeded at 264 (offset -1 lines).
patching file drivers/net/virtio/virtio_rxtx_simple.c
Hunk #2 FAILED at 120.
Hunk #3 succeeded at 366 with fuzz 1 (offset -3 lines).
Hunk #4 succeeded at 377 with fuzz 2 (offset -3 lines).
1 out of 4 hunks FAILED -- saving rejects to file drivers/net/virtio/virtio_rxtx_simple.c.rej
patching file drivers/net/virtio/virtqueue.h Hunk #2 FAILED at 183.
Hunk #3 FAILED at 192.
2 out of 3 hunks FAILED -- saving rejects to file drivers/net/virtio/virtqueue.h.rej
DPDK STV team
reply other threads:[~2016-06-13 8:40 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='9c8bee$tci26q@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=jianfeng.tan@intel.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).