From: Thomas Monjalon <thomas@monjalon.net>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: dev@dpdk.org,
Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
Dmitry Malloy <dmitrym@microsoft.com>,
Pallavi Kadam <pallavi.kadam@intel.com>,
"Menon, Ranjit" <ranjit.menon@intel.com>
Subject: Re: [dpdk-dev] [kmods PATCH 0/4] windows: independent fixes
Date: Tue, 11 Jan 2022 14:39:01 +0100 [thread overview]
Message-ID: <1900173.usQuhbGJ8B@thomas> (raw)
In-Reply-To: <b503884f-5962-ff67-4664-61fde22934eb@intel.com>
08/10/2021 04:06, Menon, Ranjit:
> On 10/2/2021 9:18 AM, Dmitry Kozlyuk wrote:
> > Fixes for building with Windows Development Kit 22000.1
> > and some build configuration cleanup.
> >
> > Dmitry Kozlyuk (4):
> > windows: specify signature hash algorithm
> > windows/virt2phys: support only x86 configurations
> > windows/virt2phys: change setup class GUID to custom
> > windows/virt2phys: add PnpLockdown directive
> >
> > windows/netuio/netuio.vcxproj | 6 ++
> > windows/virt2phys/virt2phys.inf | 3 +-
> > windows/virt2phys/virt2phys.vcxproj | 146 ++--------------------------
> > 3 files changed, 15 insertions(+), 140 deletions(-)
>
> Acked-by: Ranjit Menon <ranjit.menon@intel.com>
Applied, thanks.
prev parent reply other threads:[~2022-01-11 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 16:18 Dmitry Kozlyuk
2021-10-02 16:18 ` [dpdk-dev] [kmods PATCH 1/4] windows: specify signature hash algorithm Dmitry Kozlyuk
2021-10-02 16:18 ` [dpdk-dev] [kmods PATCH 2/4] windows/virt2phys: support only x86 configurations Dmitry Kozlyuk
2021-10-02 16:18 ` [dpdk-dev] [kmods PATCH 3/4] windows/virt2phys: change setup class GUID to custom Dmitry Kozlyuk
2021-10-02 16:18 ` [dpdk-dev] [kmods PATCH 4/4] windows/virt2phys: add PnpLockdown directive Dmitry Kozlyuk
2021-10-08 2:06 ` [dpdk-dev] [kmods PATCH 0/4] windows: independent fixes Menon, Ranjit
2022-01-11 13:39 ` 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=1900173.usQuhbGJ8B@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.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).