From: "Rob Herring (Arm)" <robh@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: linux-arm-msm@vger.kernel.org,
Akhil P Oommen <quic_akhilpo@quicinc.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH v3 5/5] dt-bindings: nvmem: qcom,qfprom: Add SAR2130P compatible
Date: Tue, 7 Jan 2025 09:14:34 -0600 [thread overview]
Message-ID: <173626287367.3576773.11518882094846922788.robh@kernel.org> (raw)
In-Reply-To: <20250104-sar2130p-nvmem-v3-5-a94e0b7de2fa@linaro.org>
On Sat, 04 Jan 2025 08:19:16 +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(+)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
prev parent reply other threads:[~2025-01-07 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 6:19 [PATCH v3 0/5] nvmem: qfprom: add Qualcomm SAR2130P support Dmitry Baryshkov
2025-01-04 6:19 ` [PATCH v3 1/5] nvmem: core: fix bit offsets of more than one byte Dmitry Baryshkov
2025-01-08 21:47 ` Akhil P Oommen
2025-01-09 4:30 ` Dmitry Baryshkov
2025-01-04 6:19 ` [PATCH v3 2/5] nvmem: core: verify cell's raw_len Dmitry Baryshkov
2025-01-04 6:19 ` [PATCH v3 3/5] nvmem: core: update raw_len if the bit reading is required Dmitry Baryshkov
2025-01-04 6:19 ` [PATCH v3 4/5] nvmem: qfprom: switch to 4-byte aligned reads Dmitry Baryshkov
2025-01-04 6:19 ` [PATCH v3 5/5] dt-bindings: nvmem: qcom,qfprom: Add SAR2130P compatible Dmitry Baryshkov
2025-01-07 15:14 ` Rob Herring (Arm) [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=173626287367.3576773.11518882094846922788.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox