From: Sascha Hauer <s.hauer@pengutronix.de>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH v2 10/15] nvmem: core: add nvmem-layout support
Date: Tue, 19 Aug 2025 14:46:16 +0200 [thread overview]
Message-ID: <aKRyGJXIcNd9oAm5@pengutronix.de> (raw)
In-Reply-To: <20250818-v2025-06-0-topic-nvmem-v2-10-b6d677f6c519@pengutronix.de>
Hi Marco,
These patches conflict with Ahmads bfetch changes. I think I fixed
this up, but please check the result.
On Mon, Aug 18, 2025 at 07:44:44PM +0200, Marco Felsch wrote:
> diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
> index 7d026330105b629e68353ae5cdbbf966284da7ea..b87dd9375c6f0a2b446e4f1c2e51c6bf042e550d 100644
> --- a/drivers/nvmem/core.c
> +++ b/drivers/nvmem/core.c
> @@ -35,6 +35,7 @@ struct nvmem_cell {
> };
>
> static LIST_HEAD(nvmem_devs);
> +static LIST_HEAD(nvmem_layouts);
During merging I realized nvmem_layouts is unused. I dropped it, but I
wonder if this variable is added accidently or if something else is
missing in this patchset?
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-08-19 15:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 17:44 [PATCH v2 00/15] NVMEM: Add support for layout drivers Marco Felsch
2025-08-18 17:44 ` [PATCH v2 01/15] of: sync of_*_phandle_with_args with Linux Marco Felsch
2025-08-18 17:44 ` [PATCH v2 02/15] of: base: add of_parse_phandle_with_optional_args() Marco Felsch
2025-08-18 17:44 ` [PATCH v2 03/15] of: device: Export of_device_make_bus_id() Marco Felsch
2025-08-18 17:44 ` [PATCH v2 04/15] nvmem: core: fix nvmem_register error path Marco Felsch
2025-08-18 17:44 ` [PATCH v2 05/15] nvmem: core: sync with Linux Marco Felsch
2025-08-20 7:32 ` Sascha Hauer
2025-08-20 9:09 ` Marco Felsch
2025-08-18 17:44 ` [PATCH v2 06/15] nvmem: core: expose nvmem cells as cdev Marco Felsch
2025-08-20 7:33 ` Sascha Hauer
2025-08-20 9:09 ` Marco Felsch
2025-08-18 17:44 ` [PATCH v2 07/15] nvmem: core: allow single and dynamic device ids Marco Felsch
2025-08-20 7:47 ` Sascha Hauer
2025-08-20 9:13 ` Marco Felsch
2025-08-18 17:44 ` [PATCH v2 08/15] eeprom: at24: fix device name handling Marco Felsch
2025-08-18 17:44 ` [PATCH v2 09/15] nvmem: core: create a header for internal sharing Marco Felsch
2025-08-18 17:44 ` [PATCH v2 10/15] nvmem: core: add nvmem-layout support Marco Felsch
2025-08-19 12:46 ` Sascha Hauer [this message]
2025-08-19 14:39 ` Marco Felsch
2025-08-20 7:41 ` Sascha Hauer
2025-08-20 9:11 ` Marco Felsch
2025-08-20 9:40 ` Sascha Hauer
2025-08-20 9:55 ` Marco Felsch
2025-08-18 17:44 ` [PATCH v2 11/15] nvmem: core: add an index parameter to the cell Marco Felsch
2025-08-18 17:44 ` [PATCH v2 12/15] nvmem: core: add per-cell post processing Marco Felsch
2025-08-18 17:44 ` [PATCH v2 13/15] nvmem: core: add cell based fixup logic Marco Felsch
2025-08-18 17:44 ` [PATCH v2 14/15] nvmem: core: provide own priv pointer in post process callback Marco Felsch
2025-08-18 17:44 ` [PATCH v2 15/15] nvmem: core: drop global cell_post_process Marco Felsch
2025-08-19 7:23 ` [PATCH v2 00/15] NVMEM: Add support for layout drivers Sascha Hauer
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=aKRyGJXIcNd9oAm5@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.felsch@pengutronix.de \
/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