All of lore.kernel.org
 help / color / mirror / Atom feed
From: <edward.cree@amd.com>
To: <davem@davemloft.net>, <kuba@kernel.org>, <edumazet@google.com>,
	<pabeni@redhat.com>
Cc: Edward Cree <ecree.xilinx@gmail.com>, <netdev@vger.kernel.org>
Subject: [PATCH v2 net 0/2] net: ethtool: fix rxfh_max_context_id
Date: Wed, 7 Aug 2024 17:06:11 +0100	[thread overview]
Message-ID: <cover.1723045898.git.ecree.xilinx@gmail.com> (raw)

From: Edward Cree <ecree.xilinx@gmail.com>

Changes in v2:
* Removed unnecessary limit==0 check, since this can never happen
* Renamed rxfh_max_context_id to rxfh_max_num_contexts
* Incremented bnxt's max to keep user-facing behaviour the same
* Added patch #2 to validate the max is sane

Patch #2 doesn't have a fixes tag because it's strictly supererogatory;
 idk if it should go to net-next instead.

Edward Cree (2):
  net: ethtool: fix off-by-one error in max RSS context IDs
  net: ethtool: check rxfh_max_num_contexts != 1 at register time

 drivers/net/ethernet/broadcom/bnxt/bnxt_ethtool.c |  2 +-
 include/linux/ethtool.h                           | 10 +++++-----
 net/ethtool/common.c                              |  2 ++
 net/ethtool/ioctl.c                               |  5 +++--
 4 files changed, 11 insertions(+), 8 deletions(-)


             reply	other threads:[~2024-08-07 16:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07 16:06 edward.cree [this message]
2024-08-07 16:06 ` [PATCH v2 net 1/2] net: ethtool: fix off-by-one error in max RSS context IDs edward.cree
2024-08-07 16:06 ` [PATCH v2 net 2/2] net: ethtool: check rxfh_max_num_contexts != 1 at register time edward.cree
2024-08-08 16:20 ` [PATCH v2 net 0/2] net: ethtool: fix rxfh_max_context_id patchwork-bot+netdevbpf
2024-08-09  3:00 ` 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.1723045898.git.ecree.xilinx@gmail.com \
    --to=edward.cree@amd.com \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.