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: <20220411120456.16edb643@xps13>
Date:   Mon, 11 Apr 2022 12:04:56 +0200
From:   Miquel Raynal <miquel.raynal@...tlin.com>
To:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:     Rafał Miłecki <zajec5@...il.com>,
        Richard Weinberger <richard@....at>,
        Vignesh Raghavendra <vigneshr@...com>,
        Tom Rini <trini@...sulko.com>, linux-mtd@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        u-boot@...ts.denx.de, devicetree@...r.kernel.org,
        Rafał Miłecki <rafal@...ecki.pl>
Subject: Re: [PATCH 2/2] nvmem: add driver handling U-Boot environment
 variables

Hi Srinivas,

srinivas.kandagatla@...aro.org wrote on Mon, 11 Apr 2022 10:45:53 +0100:

> On 11/04/2022 09:59, Miquel Raynal wrote:
> > On Wed, 2022-04-06 at 14:32:25 UTC, =?utf-8?b?UmFmYcWCIE1pxYJlY2tp?= wrote:  
> >> From: Rafał Miłecki <rafal@...ecki.pl>
> >>
> >> U-Boot stores its setup as environment variables. It's a list of
> >> key-value pairs stored on flash device with a custom header.
> >>
> >> This commit adds an NVMEM driver that:
> >> 1. Provides NVMEM access to environment vars binary data
> >> 2. Extracts variables as NVMEM cells
> >>
> >> It can be used for:
> >> 1. Accessing env variables from user-space
> >> 2. Reading NVMEM cells by Linux drivers
> >>
> >> Signed-off-by: Rafał Miłecki <rafal@...ecki.pl>  
> > 
> > Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git mtd/next, thanks.  
> 
> Hi Miquel,
> 
> Any reason why this nvmem driver is taken via mtd tree?
> 
> This is going to conflict with other nvmem patches that are touching KConfig and Makefile

Sorry I selected it by mistake. I'll let you take it through nvmem
unless there is still something missing on your side?

Anyway, it's now dropped from mtd.

Thanks,
Miquèl

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ