From: Vinod Koul <vkoul@kernel.org>
To: Iskren Chernev <iskren.chernev@gmail.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 5/8] dt-bindings: phy: qcom,qmp-ufs: Fix SM6115 clocks, regs
Date: Tue, 20 Sep 2022 11:36:49 +0530 [thread overview]
Message-ID: <YylYeSuX/99jcllf@matsya> (raw)
In-Reply-To: <20220919180618.1840194-6-iskren.chernev@gmail.com>
On 19-09-22, 21:06, Iskren Chernev wrote:
> The Sm6115 UFS PHY has 2 clocks and 3 regs.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2022-09-20 6:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 18:06 [PATCH v4 0/8] Add support for sm6115,4250 and OnePlus Nord N100 Iskren Chernev
2022-09-19 18:06 ` [PATCH v4 1/8] dt-bindings: ufs: qcom: Add sm6115 binding Iskren Chernev
2022-09-19 18:06 ` [PATCH v4 2/8] dt-bindings: arm: cpus: Add kryo240 compatible Iskren Chernev
2022-09-26 15:20 ` robh
2022-09-19 18:06 ` [PATCH v4 3/8] dt-bindings: arm: qcom: Add compatible for oneplus,billie2 phone Iskren Chernev
2022-09-19 18:06 ` [PATCH v4 4/8] dt-bindings: usb: qcom,dwc3: Fix SM6115 clocks, irqs Iskren Chernev
2022-09-19 18:06 ` [PATCH v4 5/8] dt-bindings: phy: qcom,qmp-ufs: Fix SM6115 clocks, regs Iskren Chernev
2022-09-20 6:06 ` Vinod Koul [this message]
2022-09-19 18:06 ` [PATCH v4 6/8] arm64: dts: qcom: sm6115: Add basic soc dtsi Iskren Chernev
2022-09-19 18:06 ` [PATCH v4 7/8] arm64: dts: qcom: sm4250: Add " Iskren Chernev
2022-09-19 18:06 ` [PATCH v4 8/8] arm64: dts: qcom: sm4250: Add support for oneplus-billie2 Iskren Chernev
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=YylYeSuX/99jcllf@matsya \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=iskren.chernev@gmail.com \
--cc=kishon@ti.com \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).