From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Raslan Darawsheh <rasland@mellanox.com>,
Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Asaf Penso <asafp@mellanox.com>,
Wisam Monther <wisamm@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v3] net/mlx5: add ConnectX6-DX device id
Date: Thu, 7 Nov 2019 13:40:41 +0000 [thread overview]
Message-ID: <2c47f38b-2b94-c9cf-b967-4e48395c4450@intel.com> (raw)
In-Reply-To: <DB3PR0502MB3964C2745BEC35352BFFDBBFC2780@DB3PR0502MB3964.eurprd05.prod.outlook.com>
On 11/7/2019 12:39 PM, Raslan Darawsheh wrote:
> Hi,
>
>> -----Original Message-----
>> From: dev <dev-bounces@dpdk.org> On Behalf Of Raslan Darawsheh
>> Sent: Thursday, November 7, 2019 11:36 AM
>> To: Slava Ovsiienko <viacheslavo@mellanox.com>
>> Cc: dev@dpdk.org; Asaf Penso <asafp@mellanox.com>; Wisam Monther
>> <wisamm@mellanox.com>
>> Subject: [dpdk-dev] [PATCH v3] net/mlx5: add ConnectX6-DX device id
>>
>> This adds new device id to the list of Mellanox devices
>> that runs mlx5 PMD.
>> - ConnectX-6DX device ID
>> - ConnectX-6DX SRIOV device ID
>>
>> Signed-off-by: Raslan Darawsheh <rasland@mellanox.com>
>> ---
>> v3: only set vf bit for CONNECTX6DXVF
>> v2: add missing documentation and update pci id map
>> ---
>>
>
>
> Patch applied to next-net-mlx,
>
Is supported web page [1] up to date with this information? If not can you also
send a web patch?
[1]
https://core.dpdk.org/supported/
https://core.dpdk.org/supported/nics/mellanox/
next prev parent reply other threads:[~2019-11-07 13:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 8:40 [dpdk-dev] [PATCH] " Raslan Darawsheh
2019-11-07 9:15 ` Wisam Monther
2019-11-07 9:25 ` Raslan Darawsheh
2019-11-07 9:25 ` [dpdk-dev] [PATCH v2] " Raslan Darawsheh
2019-11-07 9:36 ` [dpdk-dev] [PATCH v3] " Raslan Darawsheh
2019-11-07 11:27 ` Slava Ovsiienko
2019-11-07 12:39 ` Raslan Darawsheh
2019-11-07 13:40 ` Ferruh Yigit [this message]
2019-11-07 13:58 ` Raslan Darawsheh
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=2c47f38b-2b94-c9cf-b967-4e48395c4450@intel.com \
--to=ferruh.yigit@intel.com \
--cc=asafp@mellanox.com \
--cc=dev@dpdk.org \
--cc=rasland@mellanox.com \
--cc=viacheslavo@mellanox.com \
--cc=wisamm@mellanox.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).