From: Conor Dooley <conor@kernel.org>
To: Kathiravan T <quic_kathirav@quicinc.com>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: nvmem: qfprom: add compatible for few IPQ SoCs
Date: Fri, 26 May 2023 19:35:37 +0100 [thread overview]
Message-ID: <20230526-romp-stunned-9b3e9eb40d1e@spud> (raw)
In-Reply-To: <20230526070421.25406-2-quic_kathirav@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 262 bytes --]
On Fri, May 26, 2023 at 12:34:18PM +0530, Kathiravan T wrote:
> Add the QFPROM compatible for IPQ5332, IPQ6018 and IPQ9574
>
> Signed-off-by: Kathiravan T <quic_kathirav@quicinc.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-26 18:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 7:04 [PATCH 0/3] Add QFPROM support for few IPQ SoCs Kathiravan T
2023-05-26 7:04 ` [PATCH 1/4] dt-bindings: nvmem: qfprom: add compatible " Kathiravan T
2023-05-26 18:35 ` Conor Dooley [this message]
2023-05-26 7:04 ` [PATCH 2/4] arm64: dts: qcom: ipq5332: add QFPROM node Kathiravan T
2023-05-26 9:19 ` Konrad Dybcio
2023-05-26 10:24 ` Kathiravan T
2023-05-26 10:29 ` Konrad Dybcio
2023-05-26 7:04 ` [PATCH 3/4] arm64: dts: qcom: ipq6018: " Kathiravan T
2023-05-26 9:24 ` Konrad Dybcio
2023-05-26 10:22 ` Kathiravan T
2023-05-26 7:04 ` [PATCH 4/4] arm64: dts: qcom: ipq9574: " Kathiravan T
2023-05-26 9:19 ` Konrad Dybcio
2023-05-26 10:24 ` Kathiravan T
2023-05-26 10:29 ` Konrad Dybcio
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=20230526-romp-stunned-9b3e9eb40d1e@spud \
--to=conor@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kathirav@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
/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