From: Srinivas Kandagatla <srini@kernel.org>
To: Jingyi Wang <jingyi.wang@oss.qualcomm.com>,
Srinivas Kandagatla <srini@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: aiqun.yu@oss.qualcomm.com, tingwei.zhang@oss.qualcomm.com,
trilok.soni@oss.qualcomm.com, yijie.yang@oss.qualcomm.com,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: nvmem: qfprom: Add compatible for Qualcomm Maili
Date: Fri, 31 Jul 2026 09:21:28 +0100 [thread overview]
Message-ID: <a94d2102-9b24-41ea-a5cc-760b75f7251f@kernel.org> (raw)
In-Reply-To: <20260628-maili-qfprom-v1-1-9c097e2edfcd@oss.qualcomm.com>
On 6/29/26 7:48 AM, Jingyi Wang wrote:
> Document compatible string for the QFPROM on Qualcomm Maili platform.
>
> Signed-off-by: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
> ---
Applied 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 8134ddb54e13..72206c44feee 100644
> --- a/Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml
> +++ b/Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml
> @@ -29,6 +29,7 @@ properties:
> - qcom,ipq8074-qfprom
> - qcom,ipq9574-qfprom
> - qcom,kaanapali-qfprom
> + - qcom,maili-qfprom
> - qcom,milos-qfprom
> - qcom,msm8226-qfprom
> - qcom,msm8916-qfprom
>
> ---
> base-commit: b7bee4ca5688e30ca50fbc87b1b8f7eed7006c17
> change-id: 20260603-maili-qfprom-bb7ff3daf8a7
>
> Best regards,
prev parent reply other threads:[~2026-07-31 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 6:48 [PATCH] dt-bindings: nvmem: qfprom: Add compatible for Qualcomm Maili Jingyi Wang
2026-06-30 17:52 ` Rob Herring (Arm)
2026-07-31 8:21 ` Srinivas Kandagatla [this message]
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=a94d2102-9b24-41ea-a5cc-760b75f7251f@kernel.org \
--to=srini@kernel.org \
--cc=aiqun.yu@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jingyi.wang@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tingwei.zhang@oss.qualcomm.com \
--cc=trilok.soni@oss.qualcomm.com \
--cc=yijie.yang@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.