From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Heinrich Kuhn <heinrich.kuhn@netronome.com>, dev@dpdk.org
Cc: stable@dpdk.org, Simon Horman <simon.horman@netronome.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/nfp: fix reporting of RSS capabilities
Date: Tue, 11 May 2021 14:32:14 +0100 [thread overview]
Message-ID: <3d7d9980-de98-16e8-d47e-4b3f9f5a2871@intel.com> (raw)
In-Reply-To: <20210510164550.8888-1-heinrich.kuhn@netronome.com>
On 5/10/2021 5:45 PM, Heinrich Kuhn wrote:
> Before this change the dev_infos callback always reported RSS
> capabilities regardless of whether the capability is supported by the
> device or not. First check the capabilities field in the BAR of the
> device and advertise RSS functionality accordingly.
>
> Fixes: 8b945a7f7d ("drivers/net: update Rx RSS hash offload capabilities")
> Cc: stable@dpdk.org
>
> Signed-off-by: Heinrich Kuhn <heinrich.kuhn@netronome.com>
> Signed-off-by: Simon Horman <simon.horman@netronome.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-05-11 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 16:45 [dpdk-dev] " Heinrich Kuhn
2021-05-11 13:32 ` 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=3d7d9980-de98-16e8-d47e-4b3f9f5a2871@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=heinrich.kuhn@netronome.com \
--cc=simon.horman@netronome.com \
--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).