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  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]
Date:   Tue, 21 Aug 2018 15:33:22 +0100
From:   Srinivas Kandagatla <>
To:     Boris Brezillon <>,
        Alban <>
Cc:     Bartosz Golaszewski <>,
        Jonathan Corbet <>, Sekhar Nori <>,
        Kevin Hilman <>,
        Russell King <>,
        Arnd Bergmann <>,
        Greg Kroah-Hartman <>,
        David Woodhouse <>,
        Brian Norris <>,
        Marek Vasut <>,
        Richard Weinberger <>,
        Grygorii Strashko <>,
        "David S . Miller" <>,
        Naren <>,
        Mauro Carvalho Chehab <>,
        Andrew Morton <>,
        Lukas Wunner <>,
        Dan Carpenter <>,
        Florian Fainelli <>,
        Ivan Khoronzhuk <>,
        Sven Van Asbroeck <>,
        Paolo Abeni <>, Rob Herring <>,
        David Lechner <>,
        Andrew Lunn <>,,,,,,,,
        Bartosz Golaszewski <>
Subject: Re: [PATCH v2 06/29] mtd: Add support for reading MTD devices via the
 nvmem API

On 21/08/18 15:26, Boris Brezillon wrote:
>> This also has the side effect that nvmem cells defined in DT don't
>> appear in sysfs, unlike those defined from board code.
> Wow, that's not good. I guess we'll want to make that consistent at
> some point.
support for sysfs entries per cell is not available in nvmem. However 
there is nvmem sysfs entry per provider which can be read by the user 
space if required.


Powered by blists - more mailing lists