[PATCH 2/4] ethtool: make validate_speed accept all speeds between 0 and INT_MAX
Andy Gospodarek
gospo at cumulusnetworks.com
Thu May 12 16:07:31 UTC 2016
From: Nikolay Aleksandrov <nikolay at cumulusnetworks.com>
Devices these days can have any speed and as was recently pointed out
any speed from 0 to INT_MAX is valid so adjust speed validation to
accept such values.
Signed-off-by: Nikolay Aleksandrov <nikolay at cumulusnetworks.com>
Acked-by: Michael S. Tsirkin <mst at redhat.com>
Signed-off-by: David S. Miller <davem at davemloft.net>
(cherry picked from commit e02564ee334a7ae46b71fc18576391cb9455433e)
Signed-off-by: Andy Gospodarek <gospo at cumulusnetworks.com>
---
include/uapi/linux/ethtool.h | 19 +------------------
1 file changed, 1 insertion(+), 18 deletions(-)
diff --git a/include/uapi/linux/ethtool.h b/include/uapi/linux/ethtool.h
index 7111c24..f1b71ca 100644
--- a/include/uapi/linux/ethtool.h
+++ b/include/uapi/linux/ethtool.h
@@ -1318,24 +1318,7 @@ enum ethtool_sfeatures_retval_bits {
static inline int ethtool_validate_speed(__u32 speed)
{
- switch (speed) {
- case SPEED_10:
- case SPEED_100:
- case SPEED_1000:
- case SPEED_2500:
- case SPEED_5000:
- case SPEED_10000:
- case SPEED_20000:
- case SPEED_25000:
- case SPEED_40000:
- case SPEED_50000:
- case SPEED_56000:
- case SPEED_100000:
- case SPEED_UNKNOWN:
- return 1;
- }
-
- return 0;
+ return speed <= INT_MAX || speed == SPEED_UNKNOWN;
}
/* Duplex, half or full. */
--
2.7.4
More information about the kernel-team
mailing list