[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250403060423.1209435-1-ap420073@gmail.com>
Date: Thu, 3 Apr 2025 06:04:21 +0000
From: Taehee Yoo <ap420073@...il.com>
To: davem@...emloft.net,
kuba@...nel.org,
pabeni@...hat.com,
edumazet@...gle.com,
andrew+netdev@...n.ch,
horms@...nel.org,
shuah@...nel.org,
netdev@...r.kernel.org,
linux-kselftest@...r.kernel.org
Cc: kory.maincent@...tlin.com,
willemb@...gle.com,
aleksander.lobakin@...el.com,
ecree.xilinx@...il.com,
almasrymina@...gle.com,
daniel.zahka@...il.com,
jianbol@...dia.com,
gal@...dia.com,
michael.chan@...adcom.com,
ap420073@...il.com
Subject: [PATCH net 0/2] fix wrong hds-thresh value setting
A hds-thresh value is not set correctly if input value is 0.
The cause is that ethtool_ringparam_get_cfg(), which is a internal
function that returns ringparameters from both ->get_ringparam() and
dev->cfg can't return a correct hds-thresh value.
The first patch fixes ethtool_ringparam_get_cfg() to set hds-thresh
value correcltly.
The second patch adds random test for hds-thresh value.
So that we can test 0 value for a hds-thresh properly.
Taehee Yoo (2):
net: ethtool: fix ethtool_ringparam_get_cfg() returns a hds_thresh
value always as 0.
selftests: drv-net: test random value for hds-thresh
net/ethtool/common.c | 1 +
tools/testing/selftests/drivers/net/hds.py | 28 +++++++++++++++++++++-
2 files changed, 28 insertions(+), 1 deletion(-)
--
2.34.1
Powered by blists - more mailing lists