From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: dev@dpdk.org, Pallavi Kadam <pallavi.kadam@intel.com>
Subject: Re: [PATCH v4 1/2] windows: include winapifamily header for macros
Date: Fri, 26 Jan 2024 00:58:03 +0300 [thread overview]
Message-ID: <20240126005803.634edaf8@sovereign> (raw)
In-Reply-To: <1704757091-7964-2-git-send-email-roretzla@linux.microsoft.com>
2024-01-08 15:38 (UTC-0800), Tyler Retzlaff:
> Include winapifamily.h for WINAPI_FAMILY macro and provide a definition
> of WINAPI_FAMILY_PHONE_APP if not present (happens compiling under
> mingw)
Given this explanation, I think the subject should be:
eal/windows: make dirent.h shim compatible with MinGW
Acked-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
next prev parent reply other threads:[~2024-01-25 21:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 19:20 [PATCH] eal: initialize shared plugins on Windows Tyler Retzlaff
2023-12-07 19:20 ` Tyler Retzlaff
2023-12-07 19:43 ` Tyler Retzlaff
2023-12-07 20:26 ` [PATCH v2] " Tyler Retzlaff
2023-12-07 20:26 ` Tyler Retzlaff
2024-01-03 0:05 ` [PATCH v3] " Tyler Retzlaff
2024-01-03 0:05 ` Tyler Retzlaff
2024-01-08 23:38 ` [PATCH v4 0/2] " Tyler Retzlaff
2024-01-08 23:38 ` [PATCH v4 1/2] windows: include winapifamily header for macros Tyler Retzlaff
2024-01-25 21:58 ` Dmitry Kozlyuk [this message]
2024-01-08 23:38 ` [PATCH v4 2/2] eal: initialize shared plugins on Windows Tyler Retzlaff
2024-01-25 23:04 ` Dmitry Kozlyuk
2024-01-25 18:44 ` [PATCH v4 0/2] " Tyler Retzlaff
2024-03-12 16:52 ` [PATCH v5 " Tyler Retzlaff
2024-03-12 16:52 ` [PATCH v5 1/2] eal/windows: make dirent.h shim compatible with MinGW Tyler Retzlaff
2024-03-12 16:52 ` [PATCH v5 2/2] eal: initialize shared plugins on Windows Tyler Retzlaff
2024-05-29 14:29 ` Thomas Monjalon
2024-05-29 17:56 ` Tyler Retzlaff
2024-05-30 8:02 ` Thomas Monjalon
2024-10-03 22:44 ` Stephen Hemminger
2024-03-28 18:18 ` [PATCH v5 0/2] " Tyler Retzlaff
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=20240126005803.634edaf8@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=dev@dpdk.org \
--cc=pallavi.kadam@intel.com \
--cc=roretzla@linux.microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.