From: Thomas Monjalon <thomas@monjalon.net>
To: William Tu <u9012063@gmail.com>
Cc: dev@dpdk.org, Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
Pallavi Kadam <pallavi.kadam@intel.com>
Subject: Re: [dpdk-dev] [kmods PATCH v2] windows/netuio: add Intel device ID
Date: Tue, 11 Jan 2022 15:21:42 +0100 [thread overview]
Message-ID: <44377984.fMDQidcC6G@thomas> (raw)
In-Reply-To: <20211019190102.1903-1-u9012063@gmail.com>
19/10/2021 21:01, William Tu:
> The patch adds three Intel device IDs,
> I350 (0x1521), 82574L (0x10D3), and 82599 (0x10ED).
>
> Signed-off-by: William Tu <u9012063@gmail.com>
> Acked-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
> Acked-by: Pallavi Kadam <pallavi.kadam@intel.com>
Applied, thanks.
prev parent reply other threads:[~2022-01-11 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 18:49 [dpdk-dev] [kmods PATCH v1] windows/netuio: add Intel e1000 device IDs William Tu
2021-10-12 1:54 ` Dmitry Kozlyuk
2021-10-12 3:31 ` Kadam, Pallavi
2021-10-19 19:01 ` [dpdk-dev] [kmods PATCH v2] windows/netuio: add Intel device ID William Tu
2021-11-24 16:11 ` William Tu
2022-01-11 14:21 ` Thomas Monjalon [this message]
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=44377984.fMDQidcC6G@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=pallavi.kadam@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).