patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Raslan Darawsheh <rasland@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	 "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] common/mlx5: fix name for ConnectX VF device ID
Date: Thu, 19 Nov 2020 10:54:22 +0000	[thread overview]
Message-ID: <DM6PR12MB2748871DFAD9C577C4166CA7CFE00@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20201119080610.14294-1-rasland@nvidia.com>

Hi,

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Raslan Darawsheh
> Sent: Thursday, November 19, 2020 10:06 AM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; stable@dpdk.org
> Subject: [dpdk-dev] [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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpci-
> ids.ucw.cz%2Fv2.2%2Fpci.ids&amp;data=04%7C01%7Crasland%40nvidia.com
> %7C13be0db809fd48cf689a08d88c6214a3%7C43083d15727340c1b7db39efd9c
> cc17a%7C0%7C0%7C637413700176245747%7CUnknown%7CTWFpbGZsb3d8e
> yJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
> %7C1000&amp;sdata=0AtUwe1GPUVmOvf32LHYzyayHx%2FF7Yb7QhZKg8VL
> LB4%3D&amp;reserved=0
> 101e  ConnectX Family mlx5Gen Virtual Function
> 
> This means that all  will have the same VF device ID.
Removed extra empty space from commit log,

> 
> Fixes: 5fc66630bed5 ("net/mlx5: add ConnectX6-DX device ID")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Raslan Darawsheh <rasland@nvidia.com>
> ---
>  drivers/common/mlx5/mlx5_common.h | 2 +-
>  drivers/net/mlx5/linux/mlx5_os.c  | 2 +-
>  drivers/net/mlx5/mlx5.c           | 2 +-
>  drivers/vdpa/mlx5/mlx5_vdpa.c     | 2 +-
>  4 files changed, 4 insertions(+), 4 deletions(-)
> 
Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      parent reply	other threads:[~2020-11-19 10:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19  8:06 [dpdk-stable] " Raslan Darawsheh
2020-11-19  8:13 ` Slava Ovsiienko
2020-11-19  9:43   ` Raslan Darawsheh
2020-11-19 10:54 ` 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=DM6PR12MB2748871DFAD9C577C4166CA7CFE00@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).