From: Bjorn Andersson <andersson@kernel.org>
To: krzysztof.kozlowski+dt@linaro.org, konrad.dybcio@linaro.org,
agross@kernel.org, linux-arm-msm@vger.kernel.org,
robh+dt@kernel.org, sboyd@kernel.org, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, mturquette@baylibre.com,
robimarko@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH 1/2] clk: qcom: ipq8074: populate fw_name for usb3phy-s
Date: Wed, 18 Jan 2023 20:16:58 -0600 [thread overview]
Message-ID: <167409461440.3017003.1860190800471771653.b4-ty@kernel.org> (raw)
In-Reply-To: <20230108130440.670181-1-robimarko@gmail.com>
On Sun, 8 Jan 2023 14:04:39 +0100, Robert Marko wrote:
> Having only .name populated in parent_data for clocks which are only
> globally searchable currently will not work as the clk core won't copy
> that name if there is no .fw_name present as well.
>
> So, populate .fw_name for usb3phy clocks in parent_data as they were
> missed by me in ("clk: qcom: ipq8074: populate fw_name for all parents").
>
> [...]
Applied, thanks!
[2/2] arm64: dts: qcom: ipq8074: correct USB3 QMP PHY-s clock output names
commit: 877cff3568c0f54511d77918ae16b2d6e9a0dfce
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-01-19 2:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 13:04 Robert Marko
2023-01-08 13:04 ` [PATCH 2/2] arm64: dts: qcom: ipq8074: correct USB3 QMP PHY-s clock output names Robert Marko
2023-01-08 17:32 ` Dmitry Baryshkov
2023-01-08 18:04 ` Robert Marko
2023-01-08 18:07 ` Dmitry Baryshkov
2023-01-08 17:33 ` [PATCH 1/2] clk: qcom: ipq8074: populate fw_name for usb3phy-s Dmitry Baryshkov
2023-01-08 18:00 ` Robert Marko
2023-01-19 2:16 ` 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=167409461440.3017003.1860190800471771653.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=robimarko@gmail.com \
--cc=sboyd@kernel.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
all inboxes | Powered by JetHome®