From: "Kadam, Pallavi" <pallavi.kadam@intel.com>
To: William Tu <u9012063@gmail.com>, <dev@dpdk.org>
Cc: <david.marchand@redhat.com>, Haiyue Wang <haiyue.wang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/e1000: build on Windows
Date: Fri, 8 Oct 2021 17:02:04 -0700 [thread overview]
Message-ID: <3293ab84-c1b1-7ac7-83e0-6dc15a3cc260@intel.com> (raw)
In-Reply-To: <20211008135346.875-1-u9012063@gmail.com>
On 10/8/2021 6:53 AM, William Tu wrote:
> This patch enables building the e1000 driver for Windows.
> I tested using two Windows VM on top of VMware Fusion,
> creating two e1000 devices with device ID 0x10D3,
> verifying rx/tx works correctly using dpdk-testpmd.exe
> rxonly and txonly mode.
>
> Signed-off-by: William Tu <u9012063@gmail.com>
> Cc: Haiyue Wang <haiyue.wang@intel.com>
> ---
Tested-by: Pallavi Kadam <pallavi.kadam@intel.com>
Acked-by: Pallavi Kadam <pallavi.kadam@intel.com>
next prev parent reply other threads:[~2021-10-09 0:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 20:24 [dpdk-dev] [PATCH] " William Tu
2021-10-08 6:54 ` David Marchand
2021-10-08 6:55 ` David Marchand
2021-10-08 12:20 ` William Tu
2021-10-08 12:24 ` David Marchand
2021-10-08 13:53 ` [dpdk-dev] [PATCH v2] " William Tu
2021-10-08 16:08 ` Wang, Haiyue
2021-10-08 21:12 ` Kadam, Pallavi
2021-10-08 20:35 ` Dmitry Kozlyuk
2021-10-08 21:41 ` William Tu
2021-10-09 16:37 ` William Tu
2021-10-09 0:02 ` Kadam, Pallavi [this message]
2021-10-09 0:14 ` William Tu
2021-10-09 18:40 ` Kadam, Pallavi
2021-10-09 16:31 ` [dpdk-dev] [PATCH v3] " William Tu
2021-10-09 17:28 ` Dmitry Kozlyuk
2021-10-10 10:56 ` Wang, Haiyue
2021-10-19 19:05 ` William Tu
2021-10-19 19:12 ` Thomas Monjalon
2021-10-20 3:47 ` [dpdk-dev] [PATCH v4] " William Tu
2021-10-21 2:56 ` Zhang, Qi Z
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=3293ab84-c1b1-7ac7-83e0-6dc15a3cc260@intel.com \
--to=pallavi.kadam@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=u9012063@gmail.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).