From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [PATCH net-next] ethtool: remove ethtool_eee_use_linkmodes
Date: Tue, 5 Mar 2024 22:26:10 +0100 [thread overview]
Message-ID: <b4ff9b51-092b-4d44-bfce-c95342a05b51@gmail.com> (raw)
After 292fac464b01 ("net: ethtool: eee: Remove legacy _u32 from keee")
this function has no user any longer.
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
---
net/ethtool/common.c | 5 -----
net/ethtool/common.h | 1 -
2 files changed, 6 deletions(-)
diff --git a/net/ethtool/common.c b/net/ethtool/common.c
index ce486cec3..6b2a360dc 100644
--- a/net/ethtool/common.c
+++ b/net/ethtool/common.c
@@ -712,8 +712,3 @@ ethtool_forced_speed_maps_init(struct ethtool_forced_speed_map *maps, u32 size)
}
}
EXPORT_SYMBOL_GPL(ethtool_forced_speed_maps_init);
-
-bool ethtool_eee_use_linkmodes(const struct ethtool_keee *eee)
-{
- return !linkmode_empty(eee->supported);
-}
diff --git a/net/ethtool/common.h b/net/ethtool/common.h
index 0f2b5f7ea..28b8aaaf9 100644
--- a/net/ethtool/common.h
+++ b/net/ethtool/common.h
@@ -55,6 +55,5 @@ int ethtool_get_module_eeprom_call(struct net_device *dev,
struct ethtool_eeprom *ee, u8 *data);
bool __ethtool_dev_mm_supported(struct net_device *dev);
-bool ethtool_eee_use_linkmodes(const struct ethtool_keee *eee);
#endif /* _ETHTOOL_COMMON_H */
--
2.44.0
next reply other threads:[~2024-03-05 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 21:26 Heiner Kallweit [this message]
2024-03-05 21:43 ` [PATCH net-next] ethtool: remove ethtool_eee_use_linkmodes Andrew Lunn
2024-03-07 4:50 ` 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=b4ff9b51-092b-4d44-bfce-c95342a05b51@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox