From: Raslan Darawsheh <rasland@nvidia.com>
To: Michael Baum <michaelba@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: RE: [PATCH v2 0/2] net/mlx5: external RxQ fixes
Date: Mon, 7 Mar 2022 10:29:08 +0000 [thread overview]
Message-ID: <BYAPR12MB3078CAFC07E2CD25091BEA82CF089@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220302075823.4141453-1-michaelba@nvidia.com>
Hi,
> -----Original Message-----
> From: Michael Baum <michaelba@nvidia.com>
> Sent: Wednesday, March 2, 2022 9:58 AM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Raslan Darawsheh
> <rasland@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>
> Subject: [PATCH v2 0/2] net/mlx5: external RxQ fixes
>
> Some fixes about external RxQ support.
> They fix missing refcnt updating in some places.
>
> v2: fix typo refrencing -> referencing.
>
> Michael Baum (2):
> net/mlx5: fix external RQ dereferencing
> net/mlx5: fix external RQ referencing
>
> drivers/net/mlx5/mlx5_rxq.c | 158 ++++++++++++++++++++++--------------
> 1 file changed, 97 insertions(+), 61 deletions(-)
>
> --
> 2.25.1
Series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2022-03-07 10:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 7:47 [PATCH " Michael Baum
2022-03-02 7:48 ` [PATCH 1/2] net/mlx5: fix external RQ dereferencing Michael Baum
2022-03-02 7:48 ` [PATCH 2/2] net/mlx5: fix external RQ refrencing Michael Baum
2022-03-02 7:58 ` [PATCH v2 0/2] net/mlx5: external RxQ fixes Michael Baum
2022-03-02 7:58 ` [PATCH v2 1/2] net/mlx5: fix external RQ dereferencing Michael Baum
2022-03-02 7:58 ` [PATCH v2 2/2] net/mlx5: fix external RQ referencing Michael Baum
2022-03-07 10:29 ` 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=BYAPR12MB3078CAFC07E2CD25091BEA82CF089@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=michaelba@nvidia.com \
--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).