From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Russell King - ARM Linux <linux@armlinux.org.uk>,
Andrew Lunn <andrew@lunn.ch>, Andrew Lunn <andrew+netdev@lunn.ch>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH v2 net-next] net: phy: fixed_phy: remove link gpio support
Date: Thu, 4 Sep 2025 08:03:18 +0200 [thread overview]
Message-ID: <d618cdc8-593f-43e3-8ac1-663e2d6617d9@gmail.com> (raw)
In-Reply-To: <20250903173204.3ca4969e@kernel.org>
On 9/4/2025 2:32 AM, Jakub Kicinski wrote:
> On Tue, 2 Sep 2025 20:37:02 +0200 Heiner Kallweit wrote:
>> The only user of fixed_phy gpio functionality was here:
>> arch/arm/boot/dts/nxp/vf/vf610-zii-dev-rev-b.dts
>> Support for the switch on this board was migrated to phylink
>> (DSA - mv88e6xxx) years ago, so the functionality is unused now.
>> Therefore remove it.
>
> Sorry if I'm mixing things up and misunderstanding.
> There was a recent conversation regarding backward compat
> with device trees. Was it related to this patch? Is the policy
> that we only care about in-tree device trees?
> Would it make sense to document in the commit message?
>
This other conversation was about something different, the deprecated
old fixed-link binding. Wrt link gpio there is a very small risk
that there's out-of-tree users who use link gpio with a switch chip
not handled by DSA. I can mention this in the commit message. And yes,
my current understanding is that we care about in-tree dt's only.
prev parent reply other threads:[~2025-09-04 6:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 18:37 [PATCH v2 net-next] net: phy: fixed_phy: remove link gpio support Heiner Kallweit
2025-09-04 0:32 ` Jakub Kicinski
2025-09-04 6:03 ` Heiner Kallweit [this message]
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=d618cdc8-593f-43e3-8ac1-663e2d6617d9@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.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;
as well as URLs for NNTP newsgroup(s).