From: Thomas Monjalon <thomas@monjalon.net>
To: talshn@mellanox.com
Cc: dev@dpdk.org, dmitry.kozliuk@gmail.com,
david.marchand@redhat.com, grive@u256.net,
ranjit.menon@intel.com, navasile@linux.microsoft.com,
harini.ramakrishnan@microsoft.com, ocardona@microsoft.com,
anatoly.burakov@intel.com, "Kadam,
Pallavi" <pallavi.kadam@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] Windows bus/vdev support
Date: Wed, 09 Sep 2020 14:41:17 +0200 [thread overview]
Message-ID: <3598152.ENY12sN20H@thomas> (raw)
In-Reply-To: <3d10f4dc-65e7-6e17-3456-dfd7c46c8e2b@intel.com>
20/07/2020 21:18, Kadam, Pallavi:
>
> On 7/7/2020 1:48 AM, talshn@mellanox.com wrote:
> > From: Tal Shnaiderman <talshn@mellanox.com>
> >
> > This patchset implements the EAL functions needed for probing PMDs using vdev on Windows.
> >
> Tested-by: Pallavi Kadam <pallavi.kadam@intel.com>
Applied, thanks
next prev parent reply other threads:[~2020-09-09 12:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 14:56 [dpdk-dev] [PATCH " talshn
2020-06-24 14:56 ` [dpdk-dev] [PATCH 1/2] eal/windows: Add needed calls to detect vdev PMD talshn
2020-07-06 23:38 ` Thomas Monjalon
2020-07-07 0:43 ` Narcisa Ana Maria Vasile
2020-07-07 8:04 ` Tal Shnaiderman
2020-07-07 8:39 ` Dmitry Kozlyuk
2020-07-07 18:04 ` Ranjit Menon
2020-07-07 8:48 ` [dpdk-dev] [PATCH v2 0/2] Windows bus/vdev support talshn
2020-07-07 8:48 ` [dpdk-dev] [PATCH v2 1/2] eal/windows: add needed calls to detect vdev PMD talshn
2020-07-16 20:54 ` Narcisa Ana Maria Vasile
2020-07-07 8:48 ` [dpdk-dev] [PATCH v2 2/2] bus/vdev: build on Windows talshn
2020-07-16 20:53 ` Narcisa Ana Maria Vasile
2020-07-20 19:18 ` [dpdk-dev] [PATCH v2 0/2] Windows bus/vdev support Kadam, Pallavi
2020-09-09 12:41 ` Thomas Monjalon [this message]
2020-06-24 14:56 ` [dpdk-dev] [PATCH 2/2] bus/vdev: Windows support talshn
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=3598152.ENY12sN20H@thomas \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=grive@u256.net \
--cc=harini.ramakrishnan@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=ocardona@microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=talshn@mellanox.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).