From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: nvmem: Add compatible for SM6350
Date: Thu, 23 Mar 2023 07:13:55 +0000 [thread overview]
Message-ID: <c53239d3-75b5-a51e-ccc1-2215f1c797a8@linaro.org> (raw)
In-Reply-To: <20230314-topic-nvmem_compats-v1-1-508100c17603@linaro.org>
On 14/03/2023 13:35, Konrad Dybcio wrote:
> Docuemnt the QFPROM on SM6350.
>
> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> ---
Applied both
thanks,
srini
> Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml b/Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml
> index 2173fe82317d..cbc5a1ed7c6b 100644
> --- a/Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml
> +++ b/Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml
> @@ -32,6 +32,7 @@ properties:
> - qcom,sdm670-qfprom
> - qcom,sdm845-qfprom
> - qcom,sm6115-qfprom
> + - qcom,sm6350-qfprom
> - qcom,sm8150-qfprom
> - qcom,sm8250-qfprom
> - const: qcom,qfprom
>
next prev parent reply other threads:[~2023-03-23 7:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 13:35 [PATCH 0/2] 63(50|75) QFPROM compatibles Konrad Dybcio
2023-03-14 13:35 ` [PATCH 1/2] dt-bindings: nvmem: Add compatible for SM6350 Konrad Dybcio
2023-03-15 7:45 ` Krzysztof Kozlowski
2023-03-23 7:13 ` Srinivas Kandagatla [this message]
2023-03-14 13:35 ` [PATCH 2/2] dt-bindings: nvmem: Add compatible for SM6375 Konrad Dybcio
2023-03-15 7:46 ` Krzysztof Kozlowski
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=c53239d3-75b5-a51e-ccc1-2215f1c797a8@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@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=marijn.suijten@somainline.org \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).