From: Bjorn Andersson <andersson@kernel.org>
To: johan+linaro@kernel.org
Cc: konrad.dybcio@somainline.org, krzysztof.kozlowski+dt@linaro.org,
bmasney@redhat.com, robh+dt@kernel.org,
devicetree@vger.kernel.org, quic_shazhuss@quicinc.com,
linux-arm-msm@vger.kernel.org, agross@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH 0/2] arm64: dts: qcom: sc8280xp: fix UFS reference clocks and PHY nodes
Date: Fri, 2 Dec 2022 14:58:47 -0600 [thread overview]
Message-ID: <167001472415.2721945.17224914588032652616.b4-ty@kernel.org> (raw)
In-Reply-To: <20221104092045.17410-1-johan+linaro@kernel.org>
On Fri, 4 Nov 2022 10:20:43 +0100, Johan Hovold wrote:
> After some initial confusion, we've finally settled how the UFS ref
> clocks are used.
>
> The first patch fixes the UFS controller and PHY nodes so that they
> reflect the hardware. This one should go in 6.1-rc where the two
> previous attempts to address this are heading.
>
> [...]
Applied, thanks!
[1/2] arm64: dts: qcom: sc8280xp: fix UFS reference clocks
commit: f446022b932aff1d6a308ca5d537ec2b512debdc
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
next prev parent reply other threads:[~2022-12-02 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 9:20 [PATCH 0/2] arm64: dts: qcom: sc8280xp: fix UFS reference clocks and PHY nodes Johan Hovold
2022-11-04 9:20 ` [PATCH 1/2] arm64: dts: qcom: sc8280xp: fix UFS reference clocks Johan Hovold
2022-11-04 9:43 ` Konrad Dybcio
2022-11-07 11:09 ` Brian Masney
2022-11-07 12:23 ` Johan Hovold
2022-11-04 9:20 ` [PATCH 2/2] arm64: dts: qcom: sc8280xp: update UFS PHY nodes Johan Hovold
2022-11-04 9:41 ` Konrad Dybcio
2022-11-14 17:18 ` Brian Masney
2022-11-14 20:42 ` Brian Masney
2022-12-02 20:58 ` Bjorn Andersson [this message]
2022-12-06 18:18 ` (subset) [PATCH 0/2] arm64: dts: qcom: sc8280xp: fix UFS reference clocks and " Bjorn Andersson
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=167001472415.2721945.17224914588032652616.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=bmasney@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_shazhuss@quicinc.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.