From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: "Romain Gantois" <romain.gantois@bootlin.com>,
linux-arm-msm@vger.kernel.org, "Andrew Lunn" <andrew@lunn.ch>,
"Jakub Kicinski" <kuba@kernel.org>,
davem@davemloft.net, "Florian Fainelli" <f.fainelli@gmail.com>,
mwojtas@chromium.org, devicetree@vger.kernel.org,
"Tariq Toukan" <tariqt@nvidia.com>,
thomas.petazzoni@bootlin.com,
"Conor Dooley" <conor+dt@kernel.org>,
"Dimitri Fedrau" <dimitri.fedrau@liebherr.com>,
"Simon Horman" <horms@kernel.org>,
"Marek Behún" <kabel@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Eric Dumazet" <edumazet@google.com>,
"Herve Codina" <herve.codina@bootlin.com>,
linux-arm-kernel@lists.infradead.org,
"Paolo Abeni" <pabeni@redhat.com>,
"Daniel Golle" <daniel@makrotopia.org>,
"Köry Maincent" <kory.maincent@bootlin.com>,
"Oleksij Rempel" <o.rempel@pengutronix.de>,
"Antoine Tenart" <atenart@kernel.org>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Nicolò Veronese" <nicveronese@gmail.com>,
"Vladimir Oltean" <vladimir.oltean@nxp.com>,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
"Russell King" <linux@armlinux.org.uk>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v20 05/14] dt-bindings: net: dp83822: Deprecate ti,fiber-mode
Date: Fri, 28 Nov 2025 09:35:21 +0100 [thread overview]
Message-ID: <dff88906-d1f5-4ad1-840b-df1cbec56fc5@bootlin.com> (raw)
In-Reply-To: <176426738519.367608.14469073626442288770.robh@kernel.org>
Hi,
On 27/11/2025 19:16, Rob Herring (Arm) wrote:
>
> On Thu, 27 Nov 2025 18:17:48 +0100, Maxime Chevallier wrote:
>> The newly added ethernet-connector binding allows describing an Ethernet
>> connector with greater precision, and in a more generic manner, than
>> ti,fiber-mode. Deprecate this property.
>>
>> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
>> Reviewed-by: Christophe Leroy <christophe.leroy@csgroup.eu>
>> Tested-by: Christophe Leroy <christophe.leroy@csgroup.eu>
>> Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
>> ---
>> Documentation/devicetree/bindings/net/ti,dp83822.yaml | 9 ++++++++-
>> 1 file changed, 8 insertions(+), 1 deletion(-)
>>
>
> My bot found errors running 'make dt_binding_check' on your patch:
>
> yamllint warnings/errors:
>
> dtschema/dtc warnings/errors:
>
>
> doc reference errors (make refcheckdocs):
I don't see any error here :) maybe an issue with the bot ?
Maxime
next prev parent reply other threads:[~2025-11-28 8:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 17:17 [PATCH net-next v20 00/14] net: phy: Introduce PHY ports representation Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 01/14] dt-bindings: net: Introduce the ethernet-connector description Maxime Chevallier
2025-11-27 18:16 ` Rob Herring (Arm)
2025-11-28 8:34 ` Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 02/14] net: ethtool: Introduce ETHTOOL_LINK_MEDIUM_* values Maxime Chevallier
2025-11-27 18:02 ` Russell King (Oracle)
2025-11-27 17:17 ` [PATCH net-next v20 03/14] net: phy: Introduce PHY ports representation Maxime Chevallier
2025-11-27 18:04 ` Russell King (Oracle)
2025-11-28 8:45 ` Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 04/14] net: phy: dp83822: Add support for phy_port representation Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 05/14] dt-bindings: net: dp83822: Deprecate ti,fiber-mode Maxime Chevallier
2025-11-27 18:16 ` Rob Herring (Arm)
2025-11-28 8:35 ` Maxime Chevallier [this message]
2025-11-27 17:17 ` [PATCH net-next v20 06/14] net: phy: Create a phy_port for PHY-driven SFPs Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 07/14] net: phy: Introduce generic SFP handling for PHY drivers Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 08/14] net: phy: marvell-88x2222: Support SFP through phy_port interface Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 09/14] net: phy: marvell: " Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 10/14] net: phy: marvell10g: Support SFP through phy_port Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 11/14] net: phy: at803x: Support SFP through phy_port interface Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 12/14] net: phy: qca807x: " Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 13/14] net: phy: Only rely on phy_port for PHY-driven SFP Maxime Chevallier
2025-11-27 17:17 ` [PATCH net-next v20 14/14] Documentation: networking: Document the phy_port infrastructure Maxime Chevallier
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=dff88906-d1f5-4ad1-840b-df1cbec56fc5@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=andrew@lunn.ch \
--cc=atenart@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dimitri.fedrau@liebherr.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=herve.codina@bootlin.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kabel@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mwojtas@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=nicveronese@gmail.com \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=romain.gantois@bootlin.com \
--cc=tariqt@nvidia.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vladimir.oltean@nxp.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