From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com
Subject: Re: [PATCH v2 0/3] fix build with MinGW 13
Date: Mon, 08 Sep 2025 11:35:00 +0200 [thread overview]
Message-ID: <2379702.ElGaqSPkdT@thomas> (raw)
In-Reply-To: <20250827151759.1448018-1-thomas@monjalon.net>
27/08/2025 17:16, Thomas Monjalon:
> After an upgrade to MinGW version 13 on Arch Linux,
> some compilation errors appear in PCI, mlx5 and bbdev code.
> This series fixes them all.
>
> Bruce doesn't see them with MinGW 13.2 on OpenSUSE Tumbleweed,
> but perhaps just missing some dependencies.
>
> Thomas Monjalon (3):
> bus/pci: fix build with MinGW 13
> net/mlx5: fix build with MinGW 13
> bbdev: wrong fix for MinGW 13
>
> v2: make status_str variable local in bbdev patch
The patch for bbdev appears to be OK,
so change the title to "bbdev: fix build with MinGW 13",
and apply.
next prev parent reply other threads:[~2025-09-08 9:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 15:25 [PATCH " Thomas Monjalon
2025-08-13 15:25 ` [PATCH 1/3] bus/pci: " Thomas Monjalon
2025-08-13 15:25 ` [PATCH 2/3] net/mlx5: " Thomas Monjalon
2025-08-14 9:50 ` Dariusz Sosnowski
2025-08-13 15:25 ` [PATCH 3/3] bbdev: wrong fix for " Thomas Monjalon
2025-08-19 13:51 ` Bruce Richardson
2025-08-15 15:22 ` [PATCH 0/3] fix build with " Patrick Robb
2025-08-19 13:54 ` Bruce Richardson
2025-08-27 15:16 ` [PATCH v2 " Thomas Monjalon
2025-08-27 15:16 ` [PATCH v2 1/3] bus/pci: " Thomas Monjalon
2025-08-27 15:16 ` [PATCH v2 2/3] net/mlx5: " Thomas Monjalon
2025-08-27 15:16 ` [PATCH v2 3/3] bbdev: wrong fix for " Thomas Monjalon
2025-08-29 5:36 ` Hemant Agrawal
2025-09-08 9:35 ` Thomas Monjalon [this message]
2025-09-08 12:18 ` [PATCH v2 0/3] fix build with " Thomas Monjalon
2025-09-08 21:17 ` [PATCH v3 " Thomas Monjalon
2025-09-08 21:17 ` [PATCH v3 1/3] bus/pci: " Thomas Monjalon
2025-09-08 21:17 ` [PATCH v3 2/3] net/mlx5: " Thomas Monjalon
2025-09-08 21:17 ` [PATCH v3 3/3] bbdev: " 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=2379702.ElGaqSPkdT@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.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).