From: Krzysztof Kozlowski <krzk@kernel.org>
To: Luca Weiss <luca.weiss@fairphone.com>, linux-arm-msm@vger.kernel.org
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-scsi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] scsi: ufs: dt-bindings: Add SM6350 compatible string
Date: Sat, 19 Mar 2022 15:38:40 +0100 [thread overview]
Message-ID: <cc6a0a89-a096-e954-b245-1857e9f94c4e@kernel.org> (raw)
In-Reply-To: <20220318183004.858707-2-luca.weiss@fairphone.com>
On 18/03/2022 19:29, Luca Weiss wrote:
> Document the compatible for the UFS found on SM6350.
>
> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
> ---
> Documentation/devicetree/bindings/ufs/qcom,ufs.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-03-19 14:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 18:29 [PATCH 0/6] UFS support on SM6350 & FP4 Luca Weiss
2022-03-18 18:29 ` [PATCH 1/6] scsi: ufs: dt-bindings: Add SM6350 compatible string Luca Weiss
2022-03-19 14:38 ` Krzysztof Kozlowski [this message]
2022-03-19 14:41 ` Krzysztof Kozlowski
2022-03-21 11:48 ` Alim Akhtar
2022-03-18 18:30 ` [PATCH 2/6] dt-bindings: phy: qcom,qmp: Add SM6350 UFS PHY bindings Luca Weiss
2022-03-19 14:40 ` Krzysztof Kozlowski
2022-03-18 18:30 ` [PATCH 5/6] arm64: dts: qcom: sm6350: Add UFS nodes Luca Weiss
2022-03-19 14:43 ` Krzysztof Kozlowski
2022-03-19 18:29 ` Luca Weiss
2022-03-20 11:00 ` Krzysztof Kozlowski
2022-03-18 18:30 ` [PATCH 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=cc6a0a89-a096-e954-b245-1857e9f94c4e@kernel.org \
--to=krzk@kernel.org \
--cc=agross@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--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).