From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw68587[v10, 6/6] net/virtio: Support of VIRTIO_NET_F_SPEED_DUPLEX
Date: 18 Apr 2020 10:45:42 -0700 [thread overview]
Message-ID: <fecc85$9u1nj2@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/68587
_apply issues_
Submitter: Ivan Dyukov <i.dyukov@samsung.com>
Date: 2020-04-15 20:03:58
Reply_mail: 20200415200423.6410-7-i.dyukov@samsung.com
DPDK git baseline:
Repo:dpdk-next-net, CommitID: 82ea4f8e00bec2e7015366410dd7e88b94f15f75
Repo:dpdk, CommitID: 4e648fb70c9de2597a6987c88f0a5aa16a28a2d1
*Repo: dpdk-next-net
if (vtpci_with_feature(hw, VIRTIO_NET_F_CTRL_VQ)) {
config = &local_config;
error: patch failed: drivers/net/virtio/virtio_ethdev.c:1718
error: drivers/net/virtio/virtio_ethdev.c: patch does not apply
Checking patch drivers/net/virtio/virtio_ethdev.h...
error: while searching for:
1ULL << VIRTIO_F_RING_PACKED | \
1ULL << VIRTIO_F_IOMMU_PLATFORM | \
--
1ULL << VIRTIO_F_NOTIFICATION_DATA)
#define VIRTIO_PMD_SUPPORTED_GUEST_FEATURES \
(VIRTIO_PMD_DEFAULT_GUEST_FEATURES | \
error: patch failed: drivers/net/virtio/virtio_ethdev.h:37
error: drivers/net/virtio/virtio_ethdev.h: patch does not apply
Checking patch drivers/net/virtio/virtio_pci.h...
error: while searching for:
*/
#define VIRTIO_F_NOTIFICATION_DATA 38
/* The Guest publishes the used index for which it expects an interrupt
* at the end of the avail ring. Host should ignore the avail->flags field. */
/* The Host publishes the avail index for which it expects a kick
error: patch failed: drivers/net/virtio/virtio_pci.h:141
error: drivers/net/virtio/virtio_pci.h: patch does not apply
*Repo: dpdk
uint16_t mtu;
} __attribute__((packed));
/*
error: patch failed: drivers/net/virtio/virtio_pci.h:306
error: drivers/net/virtio/virtio_pci.h: patch does not apply
DPDK STV team
reply other threads:[~2020-04-18 17:45 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='fecc85$9u1nj2@orsmga001.jf.intel.com' \
--to=sys_stv@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).