From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: dev@dpdk.org
Cc: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
Dmitry Malloy <dmitrym@microsoft.com>,
Pallavi Kadam <pallavi.kadam@intel.com>,
Ranjit Menon <ranjit.menon@intel.com>
Subject: [dpdk-dev] [kmods PATCH 4/4] windows/virt2phys: add PnpLockdown directive
Date: Sat, 2 Oct 2021 19:18:24 +0300 [thread overview]
Message-ID: <20211002161824.19039-5-dmitry.kozliuk@gmail.com> (raw)
In-Reply-To: <20211002161824.19039-1-dmitry.kozliuk@gmail.com>
WDK for Windows 10, version 2004 emits a warning suggesting to add
PnpLockdown directive to INI [1]. Add it since virt2phys has no
potential use-cases that require modifications to driver files.
[1]: https://docs.microsoft.com/en-us/windows-hardware/drivers/install/inf-version-section
Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
---
windows/virt2phys/virt2phys.inf | 1 +
1 file changed, 1 insertion(+)
diff --git a/windows/virt2phys/virt2phys.inf b/windows/virt2phys/virt2phys.inf
index c1ea8d9..5af77d2 100644
--- a/windows/virt2phys/virt2phys.inf
+++ b/windows/virt2phys/virt2phys.inf
@@ -8,6 +8,7 @@ ClassGuid = {6d53d3f7-734b-44ec-a6a9-4e369dc121a4}
Provider = %ManufacturerName%
CatalogFile = virt2phys.cat
DriverVer =
+PnpLockdown = 1
[DestinationDirs]
DefaultDestDir = 12
--
2.29.3
next prev parent reply other threads:[~2021-10-02 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 16:18 [dpdk-dev] [kmods PATCH 0/4] windows: independent fixes 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 ` Dmitry Kozlyuk [this message]
2021-10-08 2:06 ` [dpdk-dev] [kmods PATCH 0/4] windows: independent fixes Menon, Ranjit
2022-01-11 13:39 ` Thomas Monjalon
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=20211002161824.19039-5-dmitry.kozliuk@gmail.com \
--to=dmitry.kozliuk@gmail.com \
--cc=dev@dpdk.org \
--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).