Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) client-ip=2620:137:e000::3:3;
From:   Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        linux-kernel@vger.kernel.org,
        Miquel Raynal <miquel.raynal@bootlin.com>
Cc:     Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
        Robert Marko <robert.marko@sartura.hr>,
        Luca Ceresoli <luca.ceresoli@bootlin.com>,
        Michael Walle <michael@walle.cc>,
        =?utf-8?q?Rafa=C5=82_Mi=C5=82ecki?= <rafal@milecki.pl>,
        Marco Felsch <m.felsch@pengutronix.de>,
        Randy Dunlap <rdunlap@infradead.org>,
        Chen-Yu Tsai <wenst@chromium.org>,
        Daniel Golle <daniel@makrotopia.org>
In-Reply-To: <20231129163737.698317-1-miquel.raynal@bootlin.com>
References: <20231129163737.698317-1-miquel.raynal@bootlin.com>
Subject: Re: [PATCH v14 0/8] NVMEM cells in sysfs
Message-Id: <170203247041.19230.6088380778885293722.b4-ty@linaro.org>
Date:   Fri, 08 Dec 2023 10:47:50 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk


On Wed, 29 Nov 2023 17:37:29 +0100, Miquel Raynal wrote:
> As part of a previous effort, support for dynamic NVMEM layouts was
> brought into mainline, helping a lot in getting information from NVMEM
> devices at non-static locations. One common example of NVMEM cell is the
> MAC address that must be used. Sometimes the cell content is mainly (or
> only) useful to the kernel, and sometimes it is not. Users might also
> want to know the content of cells such as: the manufacturing place and
> date, the hardware version, the unique ID, etc. Two possibilities in
> this case: either the users re-implement their own parser to go through
> the whole device and search for the information they want, or the kernel
> can expose the content of the cells if deemed relevant. This second
> approach sounds way more relevant than the first one to avoid useless
> code duplication, so here is a series bringing NVMEM cells content to
> the user through sysfs.
> 
> [...]

Applied, thanks!

[1/8] of: device: Export of_device_make_bus_id()
      commit: fae8c6013cea005d46b289177719b4f8169fad0f
[2/8] nvmem: Move of_nvmem_layout_get_container() in another header
      commit: cb46a339758f2692f7914dc5a71eda5828acac42
[3/8] nvmem: Create a header for internal sharing
      commit: c385b30e4c1dd5e24e3ed5b54eac96866f39c769
[4/8] nvmem: Simplify the ->add_cells() hook
      commit: e82d626e5acc5c352f29b9eab6fe833b367383be
[5/8] nvmem: Move and rename ->fixup_cell_info()
      commit: b596f5059da097bbc823cd93c89e807291c0fec3
[6/8] nvmem: core: Rework layouts to become regular devices
      commit: ed7778e43271c55d78ff458b826f4e989da72444
[7/8] ABI: sysfs-nvmem-cells: Expose cells through sysfs
      commit: eef7e7b605a90255622e253e092ef6da5a44405c
[8/8] nvmem: core: Expose cells through sysfs
      commit: 7e5d6434bbf3df3fae0e3d25a187be196928b663

Best regards,
-- 
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>