From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Raslan Darawsheh <rasland@nvidia.com>, dev@dpdk.org
Cc: matan@nvidia.com, viacheslavo@nvidia.com, shys@nvidia.com
Subject: Re: [dpdk-dev] [PATCH] mlx5: add ConnectX-7 and Bluefield-3 device IDs
Date: Thu, 29 Oct 2020 15:26:12 +0000 [thread overview]
Message-ID: <d6e1fcce-67d7-bd5d-92d9-3af956bb4a3c@intel.com> (raw)
In-Reply-To: <20201026114147.9566-1-rasland@nvidia.com>
On 10/26/2020 11:41 AM, Raslan Darawsheh wrote:
> This adds the ConnectX-7 and Bluefield-3 device ids to the list of
> supported Mellanox devices that run the MLX5 PMDs.
> The devices is still in development stage.
>
I assume you don't want to add these new device support to the documentation or
to the web page, but what do you think adding it to the driver documentation
with this device under development note, or experimental support etc?
> Signed-off-by: Raslan Darawsheh <rasland@nvidia.com>
<...>
next prev parent reply other threads:[~2020-10-29 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 11:41 Raslan Darawsheh
2020-10-26 13:39 ` Slava Ovsiienko
2020-10-27 7:25 ` Raslan Darawsheh
2020-10-29 15:26 ` Ferruh Yigit [this message]
2020-11-01 9:08 ` Raslan Darawsheh
2020-11-02 10:52 ` Ferruh Yigit
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=d6e1fcce-67d7-bd5d-92d9-3af956bb4a3c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=shys@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).