From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Raslan Darawsheh <rasland@nvidia.com>,
Dekel Peled <dekelp@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Shahaf Shuler <shahafs@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix RSS queue types validation
Date: Fri, 20 Nov 2020 11:24:00 +0000 [thread overview]
Message-ID: <4e28bcba-3ccc-1d81-9bb8-a23ce1d7aeda@intel.com> (raw)
In-Reply-To: <DM6PR12MB274833A8F404795834E6E08DCFE10@DM6PR12MB2748.namprd12.prod.outlook.com>
On 11/18/2020 3:34 PM, Raslan Darawsheh wrote:
> Hi,
>
>> -----Original Message-----
>> From: dev <dev-bounces@dpdk.org> On Behalf Of Dekel Peled
>> Sent: Wednesday, November 18, 2020 11:24 AM
>> To: Slava Ovsiienko <viacheslavo@nvidia.com>; Shahaf Shuler
>> <shahafs@nvidia.com>; Matan Azrad <matan@nvidia.com>
>> Cc: dev@dpdk.org
>> Subject: [dpdk-dev] [PATCH] net/mlx5: fix RSS queue types validation
>>
>> Recent patch fixed the RSS action validation, making sure hairpin queues
>> and standard queues are not used together in the same RSS action.
>> The variable used for comparison was declared and initialized within the
>> check loop, making the queue type comparison wrong.
>>
>> This patch moves the variable declaration to the start of the function,
>> outside of the check loop.
>>
>> Fixes: cb8a079aee5d ("net/mlx5: fix validate RSS queues types")
>>
>> Signed-off-by: Dekel Peled <dekelp@nvidia.com>
>> Acked-by: Ori Kam <orika@nvidia.com>
>> Acked-by: Jack Min <jackmin@nvidia.com>
>> ---
>
> Patch applied to next-net-mlx,
>
Squashed into relevant commit in next-net, thanks.
prev parent reply other threads:[~2020-11-20 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 9:24 Dekel Peled
2020-11-18 15:34 ` Raslan Darawsheh
2020-11-20 11:24 ` Ferruh Yigit [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=4e28bcba-3ccc-1d81-9bb8-a23ce1d7aeda@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dekelp@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=shahafs@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).