From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andrew Lunn <andrew+netdev@lunn.ch>,
Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>, Andrew Lunn <andrew@lunn.ch>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux-arm-msm@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-mediatek@lists.infradead.org
Subject: [PATCH net-next 0/3] net: phy: make phy_package a separate module
Date: Thu, 12 Jun 2025 23:25:00 +0200 [thread overview]
Message-ID: <eec346a4-e903-48af-8150-0191932a7a0b@gmail.com> (raw)
Only a handful of PHY drivers needs the PHY package functionality,
therefore make it a separate module which is built only if needed.
Heiner Kallweit (3):
net: phy: move __phy_package_[read|write]_mmd to phy_package.c
net: phy: make phy_package a separate module
net: phy: add Kconfig symbol PHY_PACKAGE
drivers/net/phy/Kconfig | 6 +++
drivers/net/phy/Makefile | 3 +-
drivers/net/phy/mediatek/Kconfig | 1 +
drivers/net/phy/phy-core.c | 75 +++----------------------------
drivers/net/phy/phy_package.c | 71 ++++++++++++++++++++++++++++-
drivers/net/phy/phylib-internal.h | 6 ++-
drivers/net/phy/qcom/Kconfig | 1 +
7 files changed, 91 insertions(+), 72 deletions(-)
--
2.49.0
next reply other threads:[~2025-06-12 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 21:25 Heiner Kallweit [this message]
2025-06-12 21:26 ` [PATCH net-next 1/3] net: phy: move __phy_package_[read|write]_mmd to phy_package.c Heiner Kallweit
2025-06-12 21:26 ` [PATCH net-next 2/3] net: phy: make phy_package a separate module Heiner Kallweit
2025-06-12 21:28 ` [PATCH net-next 3/3] net: phy: add Kconfig symbol PHY_PACKAGE Heiner Kallweit
2025-06-16 22:10 ` [PATCH net-next 0/3] net: phy: make phy_package a separate module 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=eec346a4-e903-48af-8150-0191932a7a0b@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--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).