On Wed, Dec 13, 2023 at 01:13:54PM +0100, Rafał Miłecki wrote: > From: Rafał Miłecki <ra...@milecki.pl> > > It's totally valid for read() to provide less bytes than requested > maximum. It may happen if there is no more data available yet or source > pushes data in small chunks. > > This actually happens when trying to read env data from NVMEM device. > Kernel may provide NVMEM content in page size parts (like 4096 B). > > This fixes warnings like: > Warning on /sys/bus/nvmem/devices/u-boot-env0/nvmem: Attempted to read 16384 > bytes but got 4096 > Warning on /sys/bus/nvmem/devices/u-boot-env0/nvmem: Attempted to read 12288 > bytes but got 4096 > Warning on /sys/bus/nvmem/devices/u-boot-env0/nvmem: Attempted to read 8192 > bytes but got 4096 > > Since the main loop in flash_read_buf() is used to read blocks this > patch adds a new nested one. > > Signed-off-by: Rafał Miłecki <ra...@milecki.pl>
Applied to u-boot/next, thanks! -- Tom
signature.asc
Description: PGP signature
