From: Ian Ray <ian.ray@gehealthcare.com>
To: Daniel Baluta <daniel.baluta@oss.nxp.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] ARM: dts: imx: bx50v3: Configure phy-mode
Date: Tue, 17 Feb 2026 15:15:14 +0200 [thread overview]
Message-ID: <aZRp4tqggA83BcYT@zeus> (raw)
In-Reply-To: <1fe4e13d-cc0f-4168-9c5d-db372433c384@oss.nxp.com>
On Tue, Feb 17, 2026 at 03:08:17PM +0200, Daniel Baluta wrote:
> CAUTION: This email originated from outside of GE HealthCare. Only open links or attachments if you trust the sender. Report suspicious emails using Outlook’s “Report” button.
>
> On 2/17/26 14:59, Ian Ray wrote:
> > Set `phy-mode' on network switch CPU ports to eliminate a warning.
>
> Can you mention in the commit message what is the warning
Apologies for not being clearer. (Checks notes.) The warning was:
-- >8 --
mv88e6085 gpio-0:00: OF node /mdio-gpio/switch@0/ports/port@4 of CPU port 4 lacks the required "phy-mode" property
-- >8 --
I will prepare a V2.
>
> and how did you get it?
>
next prev parent reply other threads:[~2026-02-17 13:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 12:59 [PATCH 0/4] ARM: dts: imx: {bx50v3,b850v3}: Update device trees Ian Ray
2026-02-17 12:59 ` [PATCH 1/4] ARM: dts: imx: bx50v3: Configure switch PHY max-speed Ian Ray
2026-02-17 14:53 ` Andrew Lunn
2026-02-17 15:07 ` Ian Ray
2026-02-17 12:59 ` [PATCH 2/4] ARM: dts: imx: bx50v3: Configure phy-mode Ian Ray
2026-02-17 13:08 ` Daniel Baluta
2026-02-17 13:15 ` Ian Ray [this message]
2026-02-17 14:58 ` Andrew Lunn
2026-02-17 15:15 ` Ian Ray
2026-02-17 12:59 ` [PATCH 3/4] ARM: dts: imx: b850v3: Define GPIO line names Ian Ray
2026-02-17 13:23 ` Daniel Baluta
2026-02-17 13:21 ` Ian Ray
2026-02-17 12:59 ` [PATCH 4/4] ARM: dts: imx: b850v3: Disable usdhc4 Ian Ray
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=aZRp4tqggA83BcYT@zeus \
--to=ian.ray@gehealthcare.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@oss.nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
/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