| 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
| ||
|
Message-ID: <566FEAE7.10109@linaro.org> Date: Tue, 15 Dec 2015 10:26:47 +0000 From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org> To: Andrew Lunn <andrew@...n.ch> CC: 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, agust@...x.de Subject: Re: [PATCH 6/6] eeprom: 93xx46: extend driver to plug into the NVMEM framework + adding Anatolij On 15/12/15 10:17, Andrew Lunn wrote: >> Is there a reason for this driver to be using the old style? >> I can understand the issues with at24/at25 but does this driver also >> suffer from such issues? > > In order to keep backwards compatibility, we need the older file in > /sys. The only other option is to remove it and see if anybody > complains about us breaking the ABI. We should atleast attempt to pitch in this direction, and ask if somebody really cares if the location of the eeprom/nvmem file matters to them? We should probably check with Anatolij Gustschin. 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 --srini > > Andrew > -- 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/
Powered by blists - more mailing lists