linux-kernel - Re: [PATCH RESEND v5 0/3] 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] [thread-next>] [day] [month] [year] [list]

Message-Id: <168924215304.14966.11949014748675344264.b4-ty@linaro.org>
Date:   Thu, 13 Jul 2023 10:55:53 +0100
From:   Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org,
        Miquel Raynal <miquel.raynal@...tlin.com>
Cc:     Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
        Robert Marko <robert.marko@...tura.hr>,
        Luka Perkov <luka.perkov@...tura.hr>
Subject: Re: [PATCH RESEND v5 0/3] NVMEM cells in sysfs


On Thu, 13 Jul 2023 09:55:04 +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/3] ABI: sysfs-nvmem-cells: Expose cells through sysfs
      commit: fbe37a7afce21f33283869f5d79901b25537c385
[2/3] nvmem: core: Create all cells before adding the nvmem device
      commit: 681e18c0a0f200c27ee72e274e572d370e957a70
[3/3] nvmem: core: Expose cells through sysfs
      commit: 757f8b3835c936a44c0f2c3f66bcd03eea96b661

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