From: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
To: Raslan Darawsheh <rasland@nvidia.com>
Cc: Thinh Tran <thinhtr@linux.vnet.ibm.com>, <dev@dpdk.org>,
<drc@linux.vnet.ibm.com>
Subject: Re: [PATCH] net/mlx5: set correct CPU socket ID for mlx5_rxq_ctrl
Date: Tue, 8 Mar 2022 14:23:15 +0200 [thread overview]
Message-ID: <20220308122315.890063-1-dkozlyuk@nvidia.com> (raw)
In-Reply-To: <BYAPR12MB3078AC9AEF124B87B582F4DECF099@BYAPR12MB3078.namprd12.prod.outlook.com>
Hi Raslan,
> Missing:
> Fixes tag:
>
> Fixes: 5ceb3a02b000 ("net/mlx5: move Rx queue DevX resource")
> Cc: xuemingl@nvidia.com
I believe the bug originates from my earlier commit, not Xueming's one:
Fixes: bc5bee028ebc ("net/mlx5: create drop queue using DevX")
next prev parent reply other threads:[~2022-03-08 12:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 22:52 Thinh Tran
2022-03-08 10:23 ` Matan Azrad
2022-03-08 12:14 ` Raslan Darawsheh
2022-03-08 12:23 ` Dmitry Kozlyuk [this message]
2022-03-08 12:25 ` Raslan Darawsheh
2022-03-09 8:50 ` Slava Ovsiienko
2022-03-09 17:10 ` Thinh Tran
2022-03-09 19:49 ` [PATCH v2] net/mlx5: fix CPU socket ID for Rx queue creation Thinh Tran
2022-03-10 9:23 ` Slava Ovsiienko
2022-03-10 9:30 ` Raslan Darawsheh
2022-03-10 15:38 ` 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=20220308122315.890063-1-dkozlyuk@nvidia.com \
--to=dkozlyuk@nvidia.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=rasland@nvidia.com \
--cc=thinhtr@linux.vnet.ibm.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).