From: Jakub Kicinski <kuba@kernel.org>
To: Minda Chen <minda.chen@starfivetech.com>
Cc: Frank <Frank.Sae@motor-comm.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next v4 3/3] net: phy: motorcomm: Add YT8522 100M RMII PHY support
Date: Wed, 20 May 2026 14:51:41 -0700 [thread overview]
Message-ID: <20260520145141.26f2930a@kernel.org> (raw)
In-Reply-To: <20260520101310.128969-4-minda.chen@starfivetech.com>
On Wed, 20 May 2026 18:13:10 +0800 Minda Chen wrote:
> Add YT8522 100M RMII ethernet PHY base driver support, including
> PHY ID and base config init function.
drivers/net/phy/motorcomm.c:1871:6: error: call to undeclared function 'of_property_read_bool'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
1871 | if (of_property_read_bool(node, "motorcomm,auto-sleep-disabled")) {
| ^
../drivers/net/phy/motorcomm.c:1871:6: note: did you mean 'fwnode_property_read_bool'?
../include/linux/property.h:59:6: note: 'fwnode_property_read_bool' declared here
59 | bool fwnode_property_read_bool(const struct fwnode_handle *fwnode,
| ^
1 error generated.
prev parent reply other threads:[~2026-05-20 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 10:13 [net-next v4 0/3] Add motorcomm 8531s set ds func and 8522 driver Minda Chen
2026-05-20 10:13 ` [net-next v4 1/3] net: phy: motorcomm: move mdio lock out from yt8531_set_ds() Minda Chen
2026-05-20 15:12 ` Andrew Lunn
2026-05-20 10:13 ` [net-next v4 2/3] net: motorcomm: phy: set drive strength in YT8531s RGMII Minda Chen
2026-05-20 15:17 ` Andrew Lunn
2026-05-20 10:13 ` [net-next v4 3/3] net: phy: motorcomm: Add YT8522 100M RMII PHY support Minda Chen
2026-05-20 15:17 ` Andrew Lunn
2026-05-20 21:51 ` Jakub Kicinski [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=20260520145141.26f2930a@kernel.org \
--to=kuba@kernel.org \
--cc=Frank.Sae@motor-comm.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=minda.chen@starfivetech.com \
--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