From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Srinivas Kandagatla" <srini@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: "Miquel Raynal" <miquel.raynal@bootlin.com>,
"Grégory Clement" <gregory.clement@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
Subject: Re: [PATCH v3 0/2] nvmem: layouts: Add fixed-layout driver
Date: Mon, 06 Jul 2026 15:37:11 +0200 [thread overview]
Message-ID: <DJRJ1XHDEB9M.W9JU7GHZX0NJ@bootlin.com> (raw)
In-Reply-To: <20260608-mathieu-nvmem-fixed-layout-v3-0-12ddc69f4c51@bootlin.com>
On Mon Jun 8, 2026 at 3:42 PM CEST, Mathieu Dubois-Briand wrote:
> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
> ---
> Changes in v3:
> - Fix device node pointer leakage
> - Move nvmem_add_cells_from_dt() prototype to internals.h
> - Enable fixed-layout as built-in by default
> - Rebased on v7.1-rc7
> - Link to v2: https://lore.kernel.org/r/20260515-mathieu-nvmem-fixed-layout-v2-0-8ac215dd4016@bootlin.com
>
> Changes in v2:
> - Fixed dependency on core layout code with CONFIG_NVMEM_LAYOUTS
> - Make fixed layout optional
> - Link to v1: https://lore.kernel.org/r/20260505-mathieu-nvmem-fixed-layout-v1-1-7f6ecbce108d@bootlin.com
>
> ---
Hi Srinivas,
Do you have any comment about this updated series?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-07-06 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 13:42 Mathieu Dubois-Briand
2026-06-08 13:42 ` [PATCH v3 1/2] " Mathieu Dubois-Briand
2026-06-08 13:42 ` [PATCH v3 2/2] nvmem: layouts: Make the fixed-layout driver optional Mathieu Dubois-Briand
2026-07-06 13:37 ` Mathieu Dubois-Briand [this message]
2026-07-16 21:41 ` [PATCH v3 0/2] nvmem: layouts: Add fixed-layout driver Srinivas Kandagatla
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=DJRJ1XHDEB9M.W9JU7GHZX0NJ@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.clement@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=srini@kernel.org \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®