linux-kernel - Re: [PATCH 6/6] eeprom: 93xx46: extend driver to plug into the NVMEM framework

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: <20151215120559.135b32a1@crub>
Date:	Tue, 15 Dec 2015 12:05:59 +0100
From:	Anatolij Gustschin <agust@...x.de>
To:	Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:	Andrew Lunn <andrew@...n.ch>, GregKH <greg@...ah.com>,
	maxime.ripard@...e-electrons.com, wsa@...-dreams.de,
	broonie@...nel.org, vz@...ia.com, afd@...com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 6/6] eeprom: 93xx46: extend driver to plug into the
 NVMEM framework

On Tue, 15 Dec 2015 10:26:47 +0000
Srinivas Kandagatla <srinivas.kandagatla@...aro.org> wrote:
...
> Anatolij, Do you see any issues if we totally move this driver to nvmem 
> framework? Which involves relocating and renameing the old eeprom file 
> to /sys/bus/nvmem/devices/*/nvmem

I don't know how many driver users are there and if breaking the
compatibility matters for them. Relocating/renaming the old eeprom
file would be acceptable for me, provided it can be accessed from
user space as before.

--
Anatolij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/