From: Srinivas Kandagatla <srini@kernel.org>
To: Chester Lin <chester62515@gmail.com>,
Dan Carpenter <dan.carpenter@linaro.org>
Cc: Ciprian Costea <ciprianmarian.costea@nxp.com>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
Ghennadi Procopciuc <ghennadi.procopciuc@oss.nxp.com>,
imx@lists.linux.dev, Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Matthias Brugger <mbrugger@suse.com>,
NXP S32 Linux Team <s32@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>
Subject: Re: (subset) [PATCH v3 0/3] nvmem: s32g-ocotp: Add driver for S32G OCOTP
Date: Thu, 04 Sep 2025 08:29:15 +0100 [thread overview]
Message-ID: <175697095597.8283.15697258146228301679.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1756800543.git.dan.carpenter@linaro.org>
On Tue, 02 Sep 2025 12:47:40 +0300, Dan Carpenter wrote:
> This driver provides a way to access the On Chip One-Time Programmable
> Controller (OCOTP) on the s32g chipset. There are three versions of this
> chip but they're compatible.
>
> v3: Mostly small cleanups. Re-order device tree entries. Remove unused
> label. Use dev_err_probe().
>
> [...]
Applied, thanks!
[1/3] dt-bindings: nvmem: Add the nxp,s32g-ocotp yaml file
commit: a3430382174a78a4a6b981feca44bcaa405e0f2c
[2/3] nvmem: s32g-ocotp: Add driver for S32G OCOTP
commit: f7605ba1859724d44a7be4994335b31666110c84
Best regards,
--
Srinivas Kandagatla <srini@kernel.org>
prev parent reply other threads:[~2025-09-04 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 9:47 [PATCH v3 0/3] nvmem: s32g-ocotp: Add driver for S32G OCOTP Dan Carpenter
2025-09-02 9:47 ` [PATCH v3 3/3] arm64: dts: s32g: Add device tree information for the OCOTP driver Dan Carpenter
2025-09-11 2:36 ` Shawn Guo
2025-09-04 7:29 ` 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=175697095597.8283.15697258146228301679.b4-ty@kernel.org \
--to=srini@kernel.org \
--cc=chester62515@gmail.com \
--cc=ciprianmarian.costea@nxp.com \
--cc=conor+dt@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=ghennadi.procopciuc@oss.nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=s32@nxp.com \
--cc=shawnguo@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