DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
	Suanming Mou <suanmingm@nvidia.com>,
	Matan Azrad <matan@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH 0/3] net/mlx5: fix mingw link issues
Date: Thu, 31 Oct 2024 08:22:19 +0000	[thread overview]
Message-ID: <CH3PR12MB8460B6B86C8C2A52CC4081CECF552@CH3PR12MB8460.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20241030105412.482107-1-dsosnowski@nvidia.com>

Hi,

From: Dariusz Sosnowski <dsosnowski@nvidia.com>
Sent: Wednesday, October 30, 2024 12:54 PM
To: Raslan Darawsheh; Slava Ovsiienko; Bing Zhao; Ori Kam; Suanming Mou; Matan Azrad
Cc: dev@dpdk.org
Subject: [PATCH 0/3] net/mlx5: fix mingw link issues

This patchset fixes link issues with MinGW which appear in next-net-mlx-main tree.
It is based on commit 69461d18dfd5 ("net/mlx5/hws: fix TC to TOS fields mapping in NAT64").

Dariusz Sosnowski (3):
  net/mlx5: fix mingw stubs link issue in flow creation
  net/mlx5: fix mingw stubs link issue in flow destroy
  net/mlx5: fix stub for HWS context validation

 drivers/net/mlx5/meson.build          |  8 +++++++-
 drivers/net/mlx5/mlx5_flow.c          |  7 -------
 drivers/net/mlx5/mlx5_flow_hw_stubs.c | 22 +++++++++++++++++-----
 3 files changed, 24 insertions(+), 13 deletions(-)

--
2.39.5


series squashed into relevant commits in next-net-mlx,

Kindest regards,
Raslan Darawsheh


      parent reply	other threads:[~2024-10-31  8:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30 10:54 Dariusz Sosnowski
2024-10-30 10:54 ` [PATCH 1/3] net/mlx5: fix mingw stubs link issue in flow creation Dariusz Sosnowski
2024-10-30 10:54 ` [PATCH 2/3] net/mlx5: fix mingw stubs link issue in flow destroy Dariusz Sosnowski
2024-10-30 10:54 ` [PATCH 3/3] net/mlx5: fix stub for HWS context validation Dariusz Sosnowski
2024-10-31  8:22 ` Raslan Darawsheh [this message]

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=CH3PR12MB8460B6B86C8C2A52CC4081CECF552@CH3PR12MB8460.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=suanmingm@nvidia.com \
    --cc=viacheslavo@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).