DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com
Subject: [PATCH v2 0/3] fix build with MinGW 13
Date: Wed, 27 Aug 2025 17:16:40 +0200	[thread overview]
Message-ID: <20250827151759.1448018-1-thomas@monjalon.net> (raw)
In-Reply-To: <20250813152829.457463-1-thomas@monjalon.net>

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

 drivers/bus/pci/windows/pci_netuio.c      | 6 ------
 drivers/bus/pci/windows/pci_netuio.h      | 4 +++-
 drivers/net/mlx5/windows/mlx5_ethdev_os.c | 2 +-
 lib/bbdev/rte_bbdev.c                     | 8 ++++++--
 4 files changed, 10 insertions(+), 10 deletions(-)

-- 
2.47.1


  parent reply	other threads:[~2025-08-27 15:18 UTC|newest]

Thread overview: 12+ 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 ` Thomas Monjalon [this message]
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

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=20250827151759.1448018-1-thomas@monjalon.net \
    --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).