From: Bjorn Andersson <andersson@kernel.org>
To: krzysztof.kozlowski+dt@linaro.org, dmitry.baryshkov@linaro.org,
sean@poorly.run, Rob Herring <robh+dt@kernel.org>,
quic_abhinavk@quicinc.com, konrad.dybcio@somainline.org,
robdclark@gmail.com, Andy Gross <agross@kernel.org>
Cc: devicetree@vger.kernel.org, airlied@linux.ie,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
swboyd@chromium.org, freedreno@lists.freedesktop.org
Subject: Re: (subset) [PATCH 0/2] arm: dts: qcom: rename HDMI PHY nodes
Date: Sun, 6 Nov 2022 21:12:00 -0600 [thread overview]
Message-ID: <166779074251.500303.3874190524418032312.b4-ty@kernel.org> (raw)
In-Reply-To: <20220924094347.178666-1-dmitry.baryshkov@linaro.org>
On Sat, 24 Sep 2022 12:43:45 +0300, Dmitry Baryshkov wrote:
> Historically HDMI PHY device tree nodes used the hdmi-phy@ names.
> Replace them with generic phy@ names.
>
> While there is no such requirement in the DT schema, it's worth doing
> that because:
>
> 1) The recent qcom DT files already use just phy@ for most of PHY nodes
>
> [...]
Applied, thanks!
[1/2] ARM: dts: qcom-apq8064: change HDMI PHY node name to generic one
commit: 5743efe0e73e4e1c8d042e982e31bb8145e35baf
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2022-11-07 3:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 9:43 [PATCH 0/2] arm: dts: qcom: rename HDMI PHY nodes Dmitry Baryshkov
2022-09-24 9:43 ` [PATCH 1/2] ARM: dts: qcom-apq8064: change HDMI PHY node name to generic one Dmitry Baryshkov
2022-09-24 14:48 ` Konrad Dybcio
2022-09-29 9:36 ` Krzysztof Kozlowski
2022-09-24 9:43 ` [PATCH 2/2] arm64: dts: qcom: msm8996: " Dmitry Baryshkov
2022-09-24 14:48 ` Konrad Dybcio
2022-09-29 9:36 ` Krzysztof Kozlowski
2022-11-07 3:12 ` Bjorn Andersson [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=166779074251.500303.3874190524418032312.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean@poorly.run \
--cc=swboyd@chromium.org \
/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;
as well as URLs for NNTP newsgroup(s).