From: Raslan Darawsheh <rasland@nvidia.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] common/mlx5: fix name for ConnectX VF device ID
Date: Thu, 19 Nov 2020 09:43:30 +0000 [thread overview]
Message-ID: <DM6PR12MB27489E5FAACBEA26AE5E6F6ACFE00@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <MWHPR12MB1501B357EDDC03F0039DF1ECDFE00@MWHPR12MB1501.namprd12.prod.outlook.com>
Hi Slava, thanks for your comments,
> -----Original Message-----
> From: Slava Ovsiienko <viacheslavo@nvidia.com>
> Sent: Thursday, November 19, 2020 10:13 AM
> To: Raslan Darawsheh <rasland@nvidia.com>; dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; stable@dpdk.org
> Subject: RE: [PATCH] common/mlx5: fix name for ConnectX VF device ID
>
> > -----Original Message-----
> > From: Raslan Darawsheh <rasland@nvidia.com>
> > Sent: Thursday, November 19, 2020 10:06
> > To: dev@dpdk.org
> > Cc: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> > <viacheslavo@nvidia.com>; stable@dpdk.org
> > Subject: [PATCH] common/mlx5: fix name for ConnectX VF device ID
> >
> > Starting ConnectX-6 Dx, the VF device ID is generic and not per chip.
> >
> > https://pci-ids.ucw.cz/v2.2/pci.ids
> > 101e ConnectX Family mlx5Gen Virtual Function
> >
> > This means that all will have the same VF device ID.
> Extra space is here: "all will".
Sure, will fix during integration.
> Beside this:
>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
>
> >
> > Fixes: 5fc66630bed5 ("net/mlx5: add ConnectX6-DX device ID")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Raslan Darawsheh <rasland@nvidia.com>
> > ---
Kindest regards,
Raslan Darawsheh
next prev parent reply other threads:[~2020-11-19 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 8:06 Raslan Darawsheh
2020-11-19 8:13 ` Slava Ovsiienko
2020-11-19 9:43 ` Raslan Darawsheh [this message]
2020-11-19 10:54 ` 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=DM6PR12MB27489E5FAACBEA26AE5E6F6ACFE00@DM6PR12MB2748.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=stable@dpdk.org \
--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).