All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: 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>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Eric Dumazet <edumazet@google.com>,
	David Miller <davem@davemloft.net>,
	"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: Re: [PATCH net-next 1/5] arm64: dts: ls1043a-qds: switch to new fixed-link binding
Date: Sat, 30 Aug 2025 23:39:58 +0200	[thread overview]
Message-ID: <d2012185-0403-4bad-ad4a-e0468e11928d@gmail.com> (raw)
In-Reply-To: <aLNst1V_OSlvpC3t@shell.armlinux.org.uk>

On 8/30/2025 11:27 PM, Russell King (Oracle) wrote:
> On Sat, Aug 30, 2025 at 12:27:23PM +0200, Heiner Kallweit wrote:
>> The old array-type fixed-link binding has been deprecated
>> for more than 10 yrs. Switch to the new binding.
> 
> ... and the fact we have device trees that use it today means that we
> can't remove support for it from the kernel.
> 
After this series there is no in-tree user of the old binding any longer.
So why shouldn't we remove support for the old binding?
Do you think of out-of-tree users, or of new dts files using the
old binding?

> I think it would make sense to update the dts files, and add a noisy
> warning when we detect that it's being used to prevent future usage.
> 

The old binding is marked deprecated in the schema, not sure whether
this results in any warning.

  fixed-link:
    oneOf:
      - $ref: /schemas/types.yaml#/definitions/uint32-array
        deprecated: true


  reply	other threads:[~2025-08-30 21:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-30 10:26 [PATCH net-next 0/5] net: phy: remove support for deprecated array-style fixed-link binding Heiner Kallweit
2025-08-30 10:27 ` [PATCH net-next 1/5] arm64: dts: ls1043a-qds: switch to new " 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 [this message]
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=d2012185-0403-4bad-ad4a-e0468e11928d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.