public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Xu <dxu@dxuuu.xyz>
To: pavan.chebbi@broadcom.com, netdev@vger.kernel.org,
	kalesh-anakkur.purayil@broadcom.com,
	linux-kselftest@vger.kernel.org, michael.chan@broadcom.com,
	linux-kernel@vger.kernel.org, kuba@kernel.org,
	martin.lau@linux.dev, ecree.xilinx@gmail.com
Cc: kernel-team@meta.com
Subject: [PATCH net v3 0/2] bnxt: Fix failure to report RSS context in ntuple rule
Date: Wed, 27 Nov 2024 15:58:28 -0700	[thread overview]
Message-ID: <cover.1732748253.git.dxu@dxuuu.xyz> (raw)

This patchset fixes a bug where bnxt driver was failing to report that
an ntuple rule is redirecting to an RSS context. First commit is the
fix, then second commit extends selftests to detect if other/new drivers
are compliant with ntuple/rss_ctx API.

=== Changelog ===

Changes from v2:
* Rebase to net instead of net-next
* Make regex work with ethtool output changes

Changes from v1:
* Add selftest in patch 2

Daniel Xu (2):
  bnxt_en: ethtool: Supply ntuple rss context action
  selftests: drv-net: rss_ctx: Add test for ntuple rule

 drivers/net/ethernet/broadcom/bnxt/bnxt_ethtool.c |  8 ++++++--
 tools/testing/selftests/drivers/net/hw/rss_ctx.py | 12 +++++++++++-
 2 files changed, 17 insertions(+), 3 deletions(-)

-- 
2.46.0


             reply	other threads:[~2024-11-27 22:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27 22:58 Daniel Xu [this message]
2024-11-27 22:58 ` [PATCH net v3 1/2] bnxt_en: ethtool: Supply ntuple rss context action Daniel Xu
2024-11-27 22:58 ` [PATCH net v3 2/2] selftests: drv-net: rss_ctx: Add test for ntuple rule Daniel Xu
2024-11-30 22:20 ` [PATCH net v3 0/2] bnxt: Fix failure to report RSS context in " patchwork-bot+netdevbpf

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=cover.1732748253.git.dxu@dxuuu.xyz \
    --to=dxu@dxuuu.xyz \
    --cc=ecree.xilinx@gmail.com \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=pavan.chebbi@broadcom.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