From: Raslan Darawsheh <rasland@nvidia.com>
To: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] common/mlx5: add ConnectX-8 device ID
Date: Wed, 26 Feb 2025 14:13:27 +0000 [thread overview]
Message-ID: <CH3PR12MB84602529F550A8DE280FFAE6CFC22@CH3PR12MB8460.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20250223071647.60542-1-rasland@nvidia.com>
Hi
From: Raslan Darawsheh <rasland@nvidia.com>
Sent: Sunday, February 23, 2025 9:16 AM
To: NBU-Contact-Thomas Monjalon (EXTERNAL)
Cc: dev@dpdk.org
Subject: [PATCH] common/mlx5: add ConnectX-8 device ID
This adds the ConnectX-8 device id to the list of
supported Nvidia devices that run the MLX5 PMDs.
Signed-off-by: Raslan Darawsheh <rasland@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2025-02-26 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-23 7:16 Raslan Darawsheh
2025-02-26 14:13 ` 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=CH3PR12MB84602529F550A8DE280FFAE6CFC22@CH3PR12MB8460.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).