From: Rob Herring <robh@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Akhil P Oommen <quic_akhilpo@quicinc.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 5/5] dt-bindings: nvmem: qcom,qfprom: Add SAR2130P compatible
Date: Tue, 4 Feb 2025 10:55:12 -0600 [thread overview]
Message-ID: <20250204165512.GA3000561-robh@kernel.org> (raw)
In-Reply-To: <20250109-sar2130p-nvmem-v4-5-633739fe5f11@linaro.org>
On Thu, Jan 09, 2025 at 06:35:49AM +0200, Dmitry Baryshkov wrote:
> Document compatible for the QFPROM on SAR2130P platform.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml | 1 +
> 1 file changed, 1 insertion(+)
As the user in the .dts is already upstream, I've applied this.
Rob
prev parent reply other threads:[~2025-02-04 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 4:35 [PATCH v4 0/5] nvmem: qfprom: add Qualcomm SAR2130P support Dmitry Baryshkov
2025-01-09 4:35 ` [PATCH v4 1/5] nvmem: core: fix bit offsets of more than one byte Dmitry Baryshkov
2025-02-04 23:40 ` Dmitry Baryshkov
2025-02-17 10:15 ` Srinivas Kandagatla
2025-01-09 4:35 ` [PATCH v4 2/5] nvmem: core: verify cell's raw_len Dmitry Baryshkov
2025-02-19 14:51 ` Mark Brown
2025-02-19 15:14 ` Dmitry Baryshkov
2025-02-20 14:18 ` Mark Brown
2025-02-20 15:50 ` Dmitry Baryshkov
2025-02-20 19:12 ` Mark Brown
2025-01-09 4:35 ` [PATCH v4 3/5] nvmem: core: update raw_len if the bit reading is required Dmitry Baryshkov
2025-01-09 4:35 ` [PATCH v4 4/5] nvmem: qfprom: switch to 4-byte aligned reads Dmitry Baryshkov
2025-01-09 4:35 ` [PATCH v4 5/5] dt-bindings: nvmem: qcom,qfprom: Add SAR2130P compatible Dmitry Baryshkov
2025-02-04 16:55 ` Rob Herring [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=20250204165512.GA3000561-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_akhilpo@quicinc.com \
--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 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.