aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/net/ethernet/intel/ice/ice_ethtool.c
diff options
context:
space:
mode:
authorJacob Keller <[email protected]>2025-05-05 20:14:22 +0000
committerTony Nguyen <[email protected]>2025-06-09 16:56:18 +0000
commit78b2d9908b42ea70e42f00af5db08ad514727a45 (patch)
treef7c57b62f071afd023ae560d1b9e9f4bafb312d8 /drivers/net/ethernet/intel/ice/ice_ethtool.c
parentMerge tag 'net-6.16-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/net... (diff)
downloadkernel-78b2d9908b42ea70e42f00af5db08ad514727a45.tar.gz
kernel-78b2d9908b42ea70e42f00af5db08ad514727a45.zip
net: intel: rename 'hena' to 'hashcfg' for clarity
i40e, ice, and iAVF all use 'hena' as a shorthand for the "hash enable" configuration. This comes originally from the X710 datasheet 'xxQF_HENA' registers. In the context of the registers the meaning is fairly clear. However, on its own, hena is a weird name that can be more difficult to understand. This is especially true in ice. The E810 hardware doesn't even have registers with HENA in the name. Replace the shorthand 'hena' with 'hashcfg'. This makes it clear the variables deal with the Hash configuration, not just a single boolean on/off for all hashing. Do not update the register names. These come directly from the datasheet for X710 and X722, and it is more important that the names can be searched. Suggested-by: Przemek Kitszel <[email protected]> Reviewed-by: Aleksandr Loktionov <[email protected]> Reviewed-by: Przemek Kitszel <[email protected]> Reviewed-by: Simon Horman <[email protected]> Signed-off-by: Jacob Keller <[email protected]> Tested-by: Rafal Romanowski <[email protected]> Tested-by: Rinitha S <[email protected]> (A Contingent worker at Intel) Signed-off-by: Tony Nguyen <[email protected]>
Diffstat (limited to 'drivers/net/ethernet/intel/ice/ice_ethtool.c')
0 files changed, 0 insertions, 0 deletions