From: Andre Muezerie <andremue@linux.microsoft.com>
To: andremue@linux.microsoft.com
Cc: dev@dpdk.org
Subject: [PATCH v3 3/3] drivers: enable drivers to be compiled with MSVC
Date: Thu, 12 Jun 2025 07:17:22 -0700 [thread overview]
Message-ID: <1749737842-30538-4-git-send-email-andremue@linux.microsoft.com> (raw)
In-Reply-To: <1749737842-30538-1-git-send-email-andremue@linux.microsoft.com>
Now that all issues related to drivers are addressed they can be
enabled to be built with MSVC.
Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>
---
drivers/meson.build | 4 ----
1 file changed, 4 deletions(-)
diff --git a/drivers/meson.build b/drivers/meson.build
index 7b7205dfac..07ff94ff26 100644
--- a/drivers/meson.build
+++ b/drivers/meson.build
@@ -1,10 +1,6 @@
# SPDX-License-Identifier: BSD-3-Clause
# Copyright(c) 2017-2019 Intel Corporation
-if is_ms_compiler
- subdir_done()
-endif
-
# Defines the order of dependencies evaluation
subdirs = [
'common',
--
2.49.0.vfs.0.3
next prev parent reply other threads:[~2025-06-12 14:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 20:11 [PATCH 0/2] remove use of non-standard array range initialization Andre Muezerie
2024-12-26 20:11 ` [PATCH 1/2] app/test: " Andre Muezerie
2024-12-26 20:11 ` [PATCH 2/2] drivers/net: " Andre Muezerie
2025-03-05 16:06 ` [PATCH v2 0/2] " Andre Muezerie
2025-03-05 16:06 ` [PATCH v2 1/2] app/test: " Andre Muezerie
2025-03-05 16:06 ` [PATCH v2 2/2] drivers/net: " Andre Muezerie
2025-03-06 3:00 ` Patrick Robb
2025-03-07 8:07 ` Howard Wang
2025-06-12 14:17 ` [PATCH v3 0/3] enable drivers to be compiled with MSVC Andre Muezerie
2025-06-12 14:17 ` [PATCH v3 1/3] app/test: remove use of non-standard array range initialization Andre Muezerie
2025-06-12 15:03 ` Bruce Richardson
2025-06-12 14:17 ` [PATCH v3 2/3] drivers/net: " Andre Muezerie
2025-06-12 14:17 ` Andre Muezerie [this message]
2025-06-13 18:55 ` [PATCH v3 3/3] drivers: enable drivers to be compiled with MSVC Patrick Robb
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=1749737842-30538-4-git-send-email-andremue@linux.microsoft.com \
--to=andremue@linux.microsoft.com \
--cc=dev@dpdk.org \
/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).