DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Tal Shnaiderman <talshn@nvidia.com>
Subject: [PATCH v2 0/4] fix Windows build with MinGW and mlx5
Date: Thu, 12 Jan 2023 21:35:42 +0100	[thread overview]
Message-ID: <20230112203546.1528465-1-thomas@monjalon.net> (raw)

The first patch is a fix for EAL Windows.
The 3 other patches are cleaning up mlx5 for Windows.
The result is to make possible to compile mlx5 on Linux for Windows.

v2: improve mlx5 doc and remove weak attribute from mlx5

Thomas Monjalon (4):
  eal/windows: fix pedantic build
  common/mlx5: get Windows dependency from standard variables
  net/mlx5: remove weak stub functions
  net/mlx5: fix Windows build with MinGW GCC 12

 doc/guides/platform/mlx5.rst                |  11 ++-
 drivers/common/mlx5/meson.build             |   4 +-
 drivers/common/mlx5/windows/meson.build     |  28 +++---
 drivers/common/mlx5/windows/mlx5_win_defs.h | 100 +++++++++++---------
 drivers/net/mlx5/meson.build                |  13 ++-
 drivers/net/mlx5/mlx5_rx.c                  |  35 -------
 drivers/net/mlx5/mlx5_rxtx_vec_null.c       |  38 ++++++++
 drivers/net/mlx5/windows/mlx5_os.c          |   4 +-
 lib/eal/windows/include/pthread.h           |   3 +-
 9 files changed, 128 insertions(+), 108 deletions(-)
 create mode 100644 drivers/net/mlx5/mlx5_rxtx_vec_null.c

-- 
2.39.0


             reply	other threads:[~2023-01-12 20:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 20:35 Thomas Monjalon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-05 16:10 [PATCH 0/3] fix mlx5 build with MinGW Thomas Monjalon
2023-01-12 20:37 ` [PATCH v2 0/4] fix Windows build with MinGW and mlx5 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=20230112203546.1528465-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=talshn@nvidia.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).