From: Vinod Koul <vkoul@kernel.org>
To: linux-mediatek@lists.infradead.org,
Eugen Hristev <eugen.hristev@collabora.com>
Cc: chunfeng.yun@mediatek.com, kishon@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
sam.shih@mediatek.com, jieyy.yang@mediatek.com,
frank-w@public-files.de, linux-arm-kernel@lists.infradead.org,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, chris.obbard@collabora.com,
kernel@collabora.com
Subject: Re: (subset) [PATCH v2 1/2] dt-bindings: phy: mediatek,tphy: allow simple nodename pattern
Date: Thu, 17 Aug 2023 15:25:33 +0530 [thread overview]
Message-ID: <169226613323.81413.1101515821069495424.b4-ty@kernel.org> (raw)
In-Reply-To: <20230814093931.9298-1-eugen.hristev@collabora.com>
On Mon, 14 Aug 2023 12:39:30 +0300, Eugen Hristev wrote:
> The pattern for the nodename only allows t-phy@... , however, for the case
> when the t-phy has no `reg` and only `ranges` (basically when the t-phy
> is just a parent node), dtc will throw this warning:
>
> Warning (unit_address_vs_reg): /t-phy@1a243000: node has a unit name, but no reg or ranges property
>
> For a node like this:
>
> [...]
Applied, thanks!
[1/2] dt-bindings: phy: mediatek,tphy: allow simple nodename pattern
commit: e4077ca4ebdefa1b4616e4dafcb67b621253b233
Best regards,
--
~Vinod
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-08-17 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 9:39 [PATCH v2 1/2] dt-bindings: phy: mediatek,tphy: allow simple nodename pattern Eugen Hristev
2023-08-14 9:39 ` [PATCH v2 2/2] arm64: dts: mediatek: fix t-phy unit name Eugen Hristev
2023-10-03 9:19 ` AngeloGioacchino Del Regno
2023-08-14 16:19 ` [PATCH v2 1/2] dt-bindings: phy: mediatek,tphy: allow simple nodename pattern Conor Dooley
2023-08-17 9:55 ` Vinod Koul [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=169226613323.81413.1101515821069495424.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chris.obbard@collabora.com \
--cc=chunfeng.yun@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eugen.hristev@collabora.com \
--cc=frank-w@public-files.de \
--cc=jieyy.yang@mediatek.com \
--cc=kernel@collabora.com \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sam.shih@mediatek.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