linux-kernel - Re: [PATCHv7 0/7] Convert exiting EEPROM drivers to NVMEM

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: <20160302005640.GA32114@kroah.com>
Date:	Wed, 02 Mar 2016 00:56:42 +0000
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Andrew Lunn <andrew@...n.ch>
Cc:	<srinivas.kandagatla@...aro.org>,
	<maxime.ripard@...e-electrons.com>, <wsa@...-dreams.de>,
	<broonie@...nel.org>, <vz@...ia.com>,
	<linux-kernel@...r.kernel.org>, <pantelis.antoniou@...sulko.com>,
	<bgolaszewski@...libre.com>
Subject: Re: [PATCHv7 0/7] Convert exiting EEPROM drivers to NVMEM

On Fri, Feb 26, 2016 at 08:59:17PM +0100, Andrew Lunn wrote:
> This patch set converts the old EEPROM drivers in driver/misc/eeprom to
> use the NVMEM framework. These drivers export there content in /sys as
> read only to root, since the EEPROM may contain sensitive information.
> So the first patch adds a flag so the NVMEM framework will create its
> file in /sys as root read only.
> 
> To keep backwards compatibility with these older drivers, the contents
> of the EEPROM must be exports in sysfs in a file called eeprom in the
> devices node in sys, where as the NVMEM places them under class/nvmem.
> So add this optional backwards compatible to the framework, again
> using a flag.
> 
> Then convert the at24, at25 and 93xx46 by adding regmap support,
> removing each drivers own /sys code and registering with the NVMEM
> framework.
> 
> Lastly, the old memory accessor mechanism has been replaced with the
> nvmem equivalent.

Nice job, all now queue up.

greg k-h