DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Maxime Leroy <maxime.leroy@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4 0/2] net/mlx5: fixes for rx queue count	calculation
Date: Tue, 17 Nov 2020 13:48:01 +0000	[thread overview]
Message-ID: <DM6PR12MB27482169DB00FE80B0643303CFE20@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20201117112648.29725-1-maxime.leroy@6wind.com>

Hi,

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Maxime Leroy
> Sent: Tuesday, November 17, 2020 1:27 PM
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v4 0/2] net/mlx5: fixes for rx queue count
> calculation
> 
> This patchset provides several bug fixes for rx queue count calculation for
> mlx5 driver.
> 
> ---
> V4:
> - fix typos in commit log
> 
> V3:
> - fix spelling mistakes
> - fix second commit for mprq case
> 
> V2:
> * squash first patch and second patch
> * fix wrong init of used for compressed cqes
> 
> Didier Pallard (1):
>   net/mlx5: fix Rx descriptor status returned value
> 
> Maxime Leroy (1):
>   net/mlx5: fix Rx queue count calculation
> 
>  drivers/net/mlx5/mlx5_rxtx.c | 21 ++++++++++++++-------
>  1 file changed, 14 insertions(+), 7 deletions(-)
> 
> --
> 2.27.0

Series applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      parent reply	other threads:[~2020-11-17 13:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17 11:26 Maxime Leroy
2020-11-17 11:26 ` [dpdk-dev] [PATCH v4 1/2] net/mlx5: fix Rx " Maxime Leroy
2020-11-17 12:06   ` Slava Ovsiienko
2020-11-17 11:26 ` [dpdk-dev] [PATCH v4 2/2] net/mlx5: fix Rx descriptor status returned value Maxime Leroy
2020-11-17 12:05   ` Slava Ovsiienko
2020-11-17 13:48 ` 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=DM6PR12MB27482169DB00FE80B0643303CFE20@DM6PR12MB2748.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=maxime.leroy@6wind.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).