From: Vinod Koul <vkoul@kernel.org>
To: Luca Weiss <luca.weiss@fairphone.com>
Cc: linux-arm-msm@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/6] phy: qcom-qmp: Add SM6350 UFS PHY support
Date: Mon, 11 Apr 2022 23:34:29 +0530 [thread overview]
Message-ID: <YlRtra5AZAw2NWMT@matsya> (raw)
In-Reply-To: <20220321133318.99406-4-luca.weiss@fairphone.com>
On 21-03-22, 14:33, Luca Weiss wrote:
> The SM6350 UFS PHY is compatible with the one from SDM845. Add a
> compatible for that.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2022-04-11 18:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 13:33 [PATCH v2 0/6] UFS support on SM6350 & FP4 Luca Weiss
2022-03-21 13:33 ` [PATCH v2 1/6] scsi: ufs: dt-bindings: Add SM6350 compatible string Luca Weiss
2022-03-21 13:40 ` Krzysztof Kozlowski
2022-03-21 15:41 ` Alim Akhtar
2022-03-21 21:45 ` Rob Herring
2022-03-21 21:45 ` Rob Herring
2022-03-21 13:33 ` [PATCH v2 2/6] dt-bindings: phy: qcom,qmp: Add SM6350 UFS PHY bindings Luca Weiss
2022-03-21 13:41 ` Krzysztof Kozlowski
2022-03-21 21:46 ` Rob Herring
2022-04-11 18:04 ` Vinod Koul
2022-03-21 13:33 ` [PATCH v2 3/6] phy: qcom-qmp: Add SM6350 UFS PHY support Luca Weiss
2022-04-11 18:04 ` Vinod Koul [this message]
2022-03-21 13:33 ` [PATCH v2 4/6] pinctrl: qcom: sm6350: fix order of UFS & SDC pins Luca Weiss
2022-03-21 14:15 ` Bjorn Andersson
2022-03-21 14:21 ` Luca Weiss
2022-04-17 23:42 ` Linus Walleij
2022-03-21 13:33 ` [PATCH v2 5/6] arm64: dts: qcom: sm6350: Add UFS nodes Luca Weiss
2022-03-21 13:42 ` Krzysztof Kozlowski
2022-03-21 13:33 ` [PATCH v2 6/6] arm64: dts: qcom: sm7225-fairphone-fp4: Enable UFS Luca Weiss
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=YlRtra5AZAw2NWMT@matsya \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=kishon@ti.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=luca.weiss@fairphone.com \
--cc=phone-devel@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