DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@mellanox.com>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix Bluefield VF type recognition
Date: Sun, 29 Sep 2019 08:57:19 +0000	[thread overview]
Message-ID: <DB3PR0502MB3964D2472D4262387F1C85A4C2830@DB3PR0502MB3964.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1569396678-5247-1-git-send-email-viacheslavo@mellanox.com>

Hi,
> -----Original Message-----
> From: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> Sent: Wednesday, September 25, 2019 10:31 AM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@mellanox.com>; Raslan Darawsheh
> <rasland@mellanox.com>; stable@dpdk.org
> Subject: [PATCH] net/mlx5: fix Bluefield VF type recognition
> 
> The PCI virtual function type was recognized correctly for Bluefield VF.
> 
> Fixes: f38c54571d62 ("net/mlx5: split PCI from generic probing")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> ---
>  drivers/net/mlx5/mlx5.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/net/mlx5/mlx5.c b/drivers/net/mlx5/mlx5.c index
> 9b5affa..06cb906 100644
> --- a/drivers/net/mlx5/mlx5.c
> +++ b/drivers/net/mlx5/mlx5.c
> @@ -2425,6 +2425,7 @@ struct mlx5_dev_spawn_data {
>  	case PCI_DEVICE_ID_MELLANOX_CONNECTX4LXVF:
>  	case PCI_DEVICE_ID_MELLANOX_CONNECTX5VF:
>  	case PCI_DEVICE_ID_MELLANOX_CONNECTX5EXVF:
> +	case PCI_DEVICE_ID_MELLANOX_CONNECTX5BFVF:
>  		dev_config.vf = 1;
>  		break;
>  	default:
> --
> 1.8.3.1



Patch applied to next-net-mlx

Kindest regards,
Raslan Darawsheh

      parent reply	other threads:[~2019-09-29  8:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25  7:31 Viacheslav Ovsiienko
2019-09-25  7:44 ` Matan Azrad
2019-09-29  8:57 ` 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=DB3PR0502MB3964D2472D4262387F1C85A4C2830@DB3PR0502MB3964.eurprd05.prod.outlook.com \
    --to=rasland@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@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).