From: Raslan Darawsheh <rasland@mellanox.com>
To: Ferruh Yigit <ferruh.yigit@intel.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:58:58 +0000 [thread overview]
Message-ID: <DB3PR0502MB3964C5E16A5A6268284FC01FC2780@DB3PR0502MB3964.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <2c47f38b-2b94-c9cf-b967-4e48395c4450@intel.com>
Hi Ferruh,
Just sent a patch for it.
http://mails.dpdk.org/archives/web/2019-November/001249.html
Kindest regards,
Raslan Darawsheh
> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> Sent: Thursday, November 7, 2019 3:41 PM
> To: Raslan Darawsheh <rasland@mellanox.com>; Slava Ovsiienko
> <viacheslavo@mellanox.com>
> Cc: 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
>
> 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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcore.
> dpdk.org%2Fsupported%2F&data=02%7C01%7Crasland%40mellanox.co
> m%7Cf52842fd310346fb709808d763881845%7Ca652971c7d2e4d9ba6a4d1492
> 56f461b%7C0%7C1%7C637087308500799095&sdata=IuJG75oSQMr6zPBc
> thp%2BGH0GTgAwL53g1m57EGSvZgg%3D&reserved=0
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcore.
> dpdk.org%2Fsupported%2Fnics%2Fmellanox%2F&data=02%7C01%7Cra
> sland%40mellanox.com%7Cf52842fd310346fb709808d763881845%7Ca652971
> c7d2e4d9ba6a4d149256f461b%7C0%7C1%7C637087308500809084&sdata
> =M2YLbet%2BFlt7XvO2IxeFtlUm0zxwasJK8NXR%2Fl9oOqk%3D&reserv
> ed=0
prev parent reply other threads:[~2019-11-07 13:59 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
2019-11-07 13:58 ` 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=DB3PR0502MB3964C5E16A5A6268284FC01FC2780@DB3PR0502MB3964.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=asafp@mellanox.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).