John Thomson ef69ab7a35 kernel: cut broken SPI_NOR 4K eraseblock LIMIT patch ... Since 4e0c54bc5b ("kernel: add support for kernel 5.4"), the spi-nor limit 4k erasesize to spi-nor chips below a configured size patch has not functioned as intended. For uniform erasesize SPI-NOR devices, both nor->erase_opcode & mtd->erasesize are used in erase operations. These are set before, and not modified by, this CONFIG_MTD_SPI_NOR_USE_4K_SECTORS_LIMIT patch. Thus, an SPI-NOR device with CONFIG_MTD_SPI_NOR_USE_4K_SECTORS will always use 4k erasesize (where the device supports it). If this patch was fixed to function as intended, there would be cases where devices change from a 4K to a 64K erasesize. Signed-off-by: John Thomson <git@johnthomson.fastmail.com.au>		2022-06-29 12:34:49 +02:00
..
backport-5.10	kernel: backport RTL8211F clkout-disable patch	2022-06-27 21:56:20 +02:00
backport-5.15	kernel: bump 5.15 to 5.15.49	2022-06-27 00:57:16 +02:00
files	kernel: update FIT partition parser to new property name	2022-04-20 15:23:02 +01:00
hack-5.10	kernel: bump 5.10 to 5.10.124	2022-06-27 00:57:15 +02:00
hack-5.15	kernel: bump 5.15 to 5.15.49	2022-06-27 00:57:16 +02:00
image	target: use SPDX license identifiers on Makefiles	2021-02-10 15:47:18 +01:00
other-files	initramfs: switch to tmpfs to fix ujail	2020-11-27 01:23:43 +00:00
pending-5.10	kernel: cut broken SPI_NOR 4K eraseblock LIMIT patch	2022-06-29 12:34:49 +02:00
pending-5.15	kernel: cut broken SPI_NOR 4K eraseblock LIMIT patch	2022-06-29 12:34:49 +02:00
config-5.10	kernel: cut broken SPI_NOR 4K eraseblock LIMIT patch	2022-06-29 12:34:49 +02:00
config-5.15	kernel: cut broken SPI_NOR 4K eraseblock LIMIT patch	2022-06-29 12:34:49 +02:00
config-filter	kernel: filter out both Clang and LLD versions	2021-12-17 16:16:34 +01:00
PATCHES	kernel: update PATCHES with a stricter policy	2013-07-09 20:52:07 +00:00