From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Stas Sergeev <stsp@list.ru>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: explicitly check in of_phy_is_fixed_link() for managed = "in-band-status"
Date: Tue, 12 Aug 2025 18:06:57 +0300 [thread overview]
Message-ID: <20250812150657.mwsnor327tepkplr@skbuf> (raw)
In-Reply-To: <aJsmkAiV7tvFEeyA@shell.armlinux.org.uk>
On Tue, Aug 12, 2025 at 12:33:36PM +0100, Russell King (Oracle) wrote:
> As an additional point, I'm not sure what has broken that justifies
> this change for the net tree. You mention at one point in the commit
> description about wanting to use "c73" as a string for "managed",
> which suggests new development, and thus shouldn't this be targetting
> net-next?
>
> Note that at present, all dts files in the kernel either omit the
> managed property, or have it present with value "in-band-status".
>
> Thus, I think the commit makes sense for net-next.
Correct, thanks for challenging this, nothing seems to be broken if
stable kernels are left alone in their thinking that managed = "c73"
would be a fixed link. It was out of caution that old and new kernels
would disagree on this when faced with the same device tree, but it does
not seem to matter. I will re-target the patch to net-next.
next prev parent reply other threads:[~2025-08-12 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 10:59 [PATCH net] net: explicitly check in of_phy_is_fixed_link() for managed = "in-band-status" Vladimir Oltean
2025-08-12 11:22 ` Russell King (Oracle)
2025-08-12 11:33 ` Russell King (Oracle)
2025-08-12 15:06 ` Vladimir Oltean [this message]
2025-08-12 11:52 ` Vladimir Oltean
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=20250812150657.mwsnor327tepkplr@skbuf \
--to=vladimir.oltean@nxp.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 \
--cc=stsp@list.ru \
/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