From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Luca Weiss <luca.weiss@fairphone.com>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v3 0/3] Fixes/improvements for SM6350 UFS
Date: Mon, 27 Oct 2025 17:37:14 -0500 [thread overview]
Message-ID: <176160465254.73268.8815685950018576928.b4-ty@kernel.org> (raw)
In-Reply-To: <20251023-sm6350-ufs-things-v3-0-b68b74e29d35@fairphone.com>
On Thu, 23 Oct 2025 13:39:25 +0200, Luca Weiss wrote:
> Fix the order of the freq-table-hz property, then convert to OPP tables
> and add interconnect support for UFS for the SM6350 SoC.
>
>
Applied, thanks!
[1/3] arm64: dts: qcom: sm6350: Fix wrong order of freq-table-hz for UFS
commit: ec9d588391761a08aab5eb4523a48ef3df2c910f
[2/3] arm64: dts: qcom: sm6350: Add OPP table support to UFSHC
commit: 06d262bcdb3bc86805739de1c484761f0a59a453
[3/3] arm64: dts: qcom: sm6350: Add interconnect support to UFS
commit: c1a45887a36ef7ded3fb4bac59d4a3445098b04b
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2025-10-27 22:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 11:39 Luca Weiss
2025-10-23 11:39 ` [PATCH v3 1/3] arm64: dts: qcom: sm6350: Fix wrong order of freq-table-hz for UFS Luca Weiss
2025-10-23 11:39 ` [PATCH v3 2/3] arm64: dts: qcom: sm6350: Add OPP table support to UFSHC Luca Weiss
2025-10-23 11:39 ` [PATCH v3 3/3] arm64: dts: qcom: sm6350: Add interconnect support to UFS Luca Weiss
2025-10-27 22:37 ` 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=176160465254.73268.8815685950018576928.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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®