linux-kernel - Re: (subset) [PATCH v9 0/7] NVMEM cells in sysfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20230817110618.623960a0@xps-13>
Date:   Thu, 17 Aug 2023 11:06:18 +0200
From:   Miquel Raynal <miquel.raynal@...tlin.com>
To:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
        Robert Marko <robert.marko@...tura.hr>,
        Luka Perkov <luka.perkov@...tura.hr>,
        Michael Walle <michael@...le.cc>, linux-kernel@...r.kernel.org,
        Randy Dunlap <rdunlap@...radead.org>,
        Chen-Yu Tsai <wenst@...omium.org>,
        Daniel Golle <daniel@...rotopia.org>,
        Rafał Miłecki <rafal@...ecki.pl>
Subject: Re: (subset) [PATCH v9 0/7] NVMEM cells in sysfs

Hi Srinivas,

srinivas.kandagatla@...aro.org wrote on Mon, 14 Aug 2023 11:01:28 +0100:

> On Tue, 08 Aug 2023 08:29:25 +0200, 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/7] nvmem: core: Create all cells before adding the nvmem device
>       commit: ad004687dafea0921c2551c7d3e7ad56837984fc
> [2/7] nvmem: core: Return NULL when no nvmem layout is found
>       commit: a29eacf7e6376a44f37cc80950c92a59ca285992
> [3/7] nvmem: core: Do not open-code existing functions
>       commit: 95735bc038a828d649fe7f66f9bb67099c18a47a
> [4/7] nvmem: core: Notify when a new layout is registered
>       commit: 0e4a8e9e49ea29af87f9f308dc3e01fab969102f

Thanks for taking these! I will soon send a v10 with a very minor
correction. I guess you prefer to merge the "major" changes right after
-rc1 so the series can spend more time in -next, or is there something
that bothers you which need additional discussion?

Thanks,
Miquèl