From: bhupesh.sharma@linaro.org
To: Anusha Rao <quic_anusha@quicinc.com>,
agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, thara.gopinath@gmail.com,
herbert@gondor.apana.org.au, davem@davemloft.net,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, mturquette@baylibre.com, sboyd@kernel.org,
p.zabel@pengutronix.de, linux-arm-msm@vger.kernel.org,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
quic_srichara@quicinc.com, quic_gokulsri@quicinc.com,
quic_sjaganat@quicinc.com, quic_kathirav@quicinc.com,
quic_arajkuma@quicinc.com, quic_poovendh@quicinc.com
Subject: Re: [PATCH V3 3/4] dt-bindings: qcom-qce: add SoC compatible string for ipq9574
Date: Mon, 22 May 2023 14:06:32 +0530 [thread overview]
Message-ID: <056fa22c-a6be-da19-1352-d771ac61ebdf@linaro.org> (raw)
In-Reply-To: <20230518141105.24741-4-quic_anusha@quicinc.com>
On 5/18/23 7:41 PM, Anusha Rao <quic_anusha@quicinc.com> wrote:
> Document the compatible string for ipq9574.
>
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> Signed-off-by: Anusha Rao <quic_anusha@quicinc.com>
> ---
> Changes in V3:
> - Picked up Acked-by tag.
>
> Documentation/devicetree/bindings/crypto/qcom-qce.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml
> index e375bd981300..0d1deae06e2d 100644
> --- a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml
> +++ b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml
> @@ -28,6 +28,7 @@ properties:
> - enum:
> - qcom,ipq6018-qce
> - qcom,ipq8074-qce
> + - qcom,ipq9574-qce
> - qcom,msm8996-qce
> - qcom,sdm845-qce
> - const: qcom,ipq4019-qce
Reviewed-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
Thanks.
next prev parent reply other threads:[~2023-05-22 8:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 14:11 [PATCH V3 0/4] Enable crypto for ipq9574 Anusha Rao
2023-05-18 14:11 ` [PATCH V3 1/4] dt-bindings: clock: Add crypto clock and reset definitions Anusha Rao
2023-05-22 8:35 ` bhupesh.sharma
2023-05-18 14:11 ` [PATCH V3 2/4] clk: qcom: gcc-ipq9574: Enable crypto clocks Anusha Rao
2023-05-22 8:58 ` bhupesh.sharma
2023-05-24 5:31 ` Anusha Canchi
2023-05-18 14:11 ` [PATCH V3 3/4] dt-bindings: qcom-qce: add SoC compatible string for ipq9574 Anusha Rao
2023-05-22 8:36 ` bhupesh.sharma [this message]
2023-05-18 14:11 ` [PATCH V3 4/4] arm64: dts: qcom: ipq9574: Enable crypto nodes Anusha Rao
2023-05-18 14:43 ` Krzysztof Kozlowski
2023-05-22 8:53 ` bhupesh.sharma
2023-05-24 5:27 ` Anusha Canchi
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=056fa22c-a6be-da19-1352-d771ac61ebdf@linaro.org \
--to=bhupesh.sharma@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=quic_anusha@quicinc.com \
--cc=quic_arajkuma@quicinc.com \
--cc=quic_gokulsri@quicinc.com \
--cc=quic_kathirav@quicinc.com \
--cc=quic_poovendh@quicinc.com \
--cc=quic_sjaganat@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=thara.gopinath@gmail.com \
/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).