From: Bjorn Andersson <andersson@kernel.org>
To: Alexander Koskovich <akoskovich@pm.me>
Cc: Srinivas Kandagatla <srini@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Luca Weiss <luca.weiss@fairphone.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: nvmem: qfprom: Add Milos compatible
Date: Tue, 12 May 2026 15:47:33 -0500 [thread overview]
Message-ID: <agOR3GXg-tMcNipL@baldur> (raw)
In-Reply-To: <20260331-milos-qfprom-v1-1-36017cc642db@pm.me>
On Wed, Apr 01, 2026 at 02:24:57AM +0000, Alexander Koskovich wrote:
> Document compatible string for the QFPROM on Milos platform.
>
> Signed-off-by: Alexander Koskovich <akoskovich@pm.me>
Reviewed-by: Bjorn Andersson <andersson@kernel.org>
> ---
> 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 839513d4b499..936878e74895 100644
> --- a/Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml
> +++ b/Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml
> @@ -26,6 +26,7 @@ properties:
> - qcom,ipq8064-qfprom
> - qcom,ipq8074-qfprom
> - qcom,ipq9574-qfprom
> + - qcom,milos-qfprom
> - qcom,msm8226-qfprom
> - qcom,msm8916-qfprom
> - qcom,msm8917-qfprom
>
> --
> 2.53.0
>
>
next prev parent reply other threads:[~2026-05-12 20:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 2:24 [PATCH 0/2] arm64: dts: qcom: milos: Add QFPROM efuse support Alexander Koskovich
2026-04-01 2:24 ` [PATCH 1/2] dt-bindings: nvmem: qfprom: Add Milos compatible Alexander Koskovich
2026-04-01 10:55 ` Krzysztof Kozlowski
2026-05-12 20:47 ` Bjorn Andersson [this message]
2026-04-01 2:25 ` [PATCH 2/2] arm64: dts: qcom: milos: Add qfprom efuse node Alexander Koskovich
2026-04-01 9:41 ` Konrad Dybcio
2026-04-01 11:16 ` Dmitry Baryshkov
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=agOR3GXg-tMcNipL@baldur \
--to=andersson@kernel.org \
--cc=akoskovich@pm.me \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=robh@kernel.org \
--cc=srini@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