On Thu, Apr 25, 2019 at 9:44 PM Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > On Sat, Mar 30, 2019 at 03:16:37PM +0100, Boris Brezillon wrote: > > The AT25 protocol fits pretty well in the spi-mem model. Convert the > > at25 spi driver to a spi-mem driver and use the dirmap API instead of > > forging SPI messages manually. > > This makes the driver compatible with spi-mem-only controllers > > (controllers implementing only the spi_mem ops). > > > > Cc: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> > > Signed-off-by: Boris Brezillon <boris.brezillon@xxxxxxxxxxxxx> > > --- > > drivers/misc/eeprom/at25.c | 282 +++++++++++++++++++++++-------------- > > 1 file changed, 176 insertions(+), 106 deletions(-) > > Will there be a new version of this to fix up the problems that 0-day > found in it? gmail-whitespace-damaged fix: diff --git a/drivers/misc/eeprom/Kconfig b/drivers/misc/eeprom/Kconfig index f2abe27010eff133..98145d7d43d0c728 100644 --- a/drivers/misc/eeprom/Kconfig +++ b/drivers/misc/eeprom/Kconfig @@ -36,6 +36,7 @@ config EEPROM_AT25 depends on SPI && SYSFS select NVMEM select NVMEM_SYSFS + select SPI_MEM help Enable this driver to get read/write support to most SPI EEPROMs, after you configure the board init code to know about each eeprom Boris: what's the plan? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds