From: Christian Marangi <ansuelsmth@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Christian Marangi <ansuelsmth@gmail.com>
Subject: [net-next PATCH v2 0/3] net: add define to describe link speed modes
Date: Thu, 14 Dec 2023 16:49:03 +0100 [thread overview]
Message-ID: <20231214154906.29436-1-ansuelsmth@gmail.com> (raw)
This is a simple series to add a way to describe link speed modes number.
An additional helper is added and the phy_speeds is better documented
and expanded to return just the modes number.
This is also needed in the upcoming changes in the netdev trigger for LEDs
where phy_speeds functions is used to declare a more compact array instead
of using a "big enough" approach.
Changes v2:
- Drop stupid enum-define hack
- Introduce helper function
- Document phy_speeds function
- Extent phy_speeds function
Christian Marangi (3):
net: phy: refactor and better document phy_speeds function
net: phy: add simple helper to return count of supported speeds
net: phy: led: dynamically allocate speed modes array
drivers/net/phy/phy-core.c | 50 +++++++++++++++++++++++++++---
drivers/net/phy/phy.c | 12 +++++++
drivers/net/phy/phy_led_triggers.c | 16 ++++++++--
3 files changed, 70 insertions(+), 8 deletions(-)
--
2.40.1
next reply other threads:[~2023-12-14 22:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 15:49 Christian Marangi [this message]
2023-12-14 15:49 ` [net-next PATCH v2 1/3] net: phy: refactor and better document phy_speeds function Christian Marangi
2023-12-14 15:49 ` [net-next PATCH v2 2/3] net: phy: add simple helper to return count of supported speeds Christian Marangi
2023-12-15 12:16 ` kernel test robot
2023-12-14 15:49 ` [net-next PATCH v2 3/3] net: phy: led: dynamically allocate speed modes array Christian Marangi
2023-12-15 12:50 ` kernel test robot
2023-12-17 1:12 ` Christian Marangi
2023-12-17 10:38 ` Russell King (Oracle)
2023-12-17 12:12 ` Christian Marangi
2023-12-15 12:50 ` kernel test robot
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=20231214154906.29436-1-ansuelsmth@gmail.com \
--to=ansuelsmth@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).