From: Heiner Kallweit <hkallweit1@gmail.com>
To: Shawn Guo <shawnguo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Patrice Chotard <patrice.chotard@foss.st.com>,
Andrew Lunn <andrew@lunn.ch>, Andrew Lunn <andrew+netdev@lunn.ch>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
David Miller <davem@davemloft.net>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [PATCH net-next 0/5] net: phy: remove support for deprecated array-style fixed-link binding
Date: Sat, 30 Aug 2025 12:26:24 +0200 [thread overview]
Message-ID: <a3c2f8d3-36e6-4411-9526-78abbc60e1da@gmail.com> (raw)
The array-style fixed-link binding has been marked deprecated for more
than 10 yrs. See e.g. 91c1d980d601 ("Documentation: devicetree: add old
and deprecated 'fixed-link'") from 2014.
So migrate the remaining few in-kernel users of the old binding,
and remove for it.
Heiner Kallweit (5):
arm64: dts: ls1043a-qds: switch to new fixed-link binding
ARM: dts: ls1021a: switch to new fixed-link binding
ARM: dts: st: switch to new fixed-link binding
net: mdio: remove support for old fixed-link binding
net: phy: phylink: remove support for deprecated fixed-link-binding
arch/arm/boot/dts/nxp/ls/ls1021a-iot.dts | 5 +++-
arch/arm/boot/dts/st/stih418-b2199.dts | 5 +++-
arch/arm/boot/dts/st/stihxxx-b2120.dtsi | 5 +++-
.../boot/dts/freescale/fsl-ls1043a-qds.dts | 5 +++-
drivers/net/mdio/of_mdio.c | 26 -------------------
drivers/net/phy/phylink.c | 25 +-----------------
6 files changed, 17 insertions(+), 54 deletions(-)
--
2.51.0
next reply other threads:[~2025-08-30 10:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 10:26 Heiner Kallweit [this message]
2025-08-30 10:27 ` [PATCH net-next 1/5] arm64: dts: ls1043a-qds: switch to new fixed-link binding Heiner Kallweit
2025-08-30 15:40 ` kernel test robot
2025-08-30 21:27 ` Russell King (Oracle)
2025-08-30 21:39 ` Heiner Kallweit
2025-08-30 21:44 ` Russell King (Oracle)
2025-09-01 19:39 ` Heiner Kallweit
2025-09-01 22:47 ` Andrew Lunn
2025-08-30 10:28 ` [PATCH net-next 2/5] ARM: dts: ls1021a: " Heiner Kallweit
2025-08-30 15:41 ` kernel test robot
2025-08-30 10:28 ` [PATCH net-next 3/5] ARM: dts: st: " Heiner Kallweit
2025-08-30 10:29 ` [PATCH net-next 4/5] net: mdio: remove support for old " Heiner Kallweit
2025-08-30 10:31 ` [PATCH net-next 5/5] net: phy: phylink: remove support for deprecated " Heiner Kallweit
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=a3c2f8d3-36e6-4411-9526-78abbc60e1da@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patrice.chotard@foss.st.com \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
/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).