From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Artemii Morozov <artemii.morozov@arknetworks.am>, dev@dpdk.org
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
stable@dpdk.org, Andy Moreton <amoreton@xilinx.com>
Subject: Re: [PATCH v5] common/sfc_efx/base: fix Rx queue creation without RSS hash prefix
Date: Thu, 22 Jun 2023 16:06:52 +0100 [thread overview]
Message-ID: <0ed0aa00-d46e-37f3-251d-96195cb36218@amd.com> (raw)
In-Reply-To: <20230622123136.264482-1-artemii.morozov@arknetworks.am>
On 6/22/2023 1:31 PM, Artemii Morozov wrote:
> If the prefix for the RSS hash was not chosen the ENOTSUP error should
> be returned.
>
> Before this patch success was returned for this case causing Rx queue
> creation to fail.
>
> Fixing return value to indicate failure.
>
> Fixes: f784cdc5cbb1 ("common/sfc_efx/base: provide control to deliver RSS hash")
> Cc: stable@dpdk.org
>
> Signed-off-by: Artemii Morozov <artemii.morozov@arknetworks.am>
> Reviewed-by: Andy Moreton <amoreton@xilinx.com>
> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-06-22 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 7:08 [PATCH] common/sfc_efx/base: set return code in case of the error Artemii Morozov
2023-06-01 6:30 ` [PATCH v2] " Artemii Morozov
2023-06-01 15:48 ` Ferruh Yigit
2023-06-22 9:13 ` [PATCH v3] " Artemii Morozov
2023-06-22 9:25 ` Andrew Rybchenko
2023-06-22 9:31 ` [PATCH v4] " Artemii Morozov
2023-06-22 11:27 ` Ferruh Yigit
2023-06-22 12:31 ` [PATCH v5] common/sfc_efx/base: fix Rx queue creation without RSS hash prefix Artemii Morozov
2023-06-22 13:13 ` Ferruh Yigit
2023-06-22 13:52 ` Artemii Morozov
2023-06-22 15:06 ` 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=0ed0aa00-d46e-37f3-251d-96195cb36218@amd.com \
--to=ferruh.yigit@amd.com \
--cc=amoreton@xilinx.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=artemii.morozov@arknetworks.am \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).