On 19/02/2020 10.47, Rasmus Villemoes wrote: > The various env storage drivers almost all have their own logic [1] > for deciding whether to compile and provide the .save method, many of > which fail to honour CONFIG_SPL_SAVEENV. For example, fat.c and sf.c > define a CMD_SAVEENV macro only for !CONFIG_SPL_BUILD, while ext4.c > "only" depends on CONFIG_CMD_SAVEENV - but CONFIG_SPL_SAVEENV=y, > CONFIG_CMD_SAVEENV=n is a valid combination. > > A lot of that ifdeffery can be removed while at the same time > providing the .save method if either CONFIG_SPL_SAVEENV (for an SPL > build) or CONFIG_CMD_SAVEENV (for U-Boot proper) is set. The first two > patches introduce infrastructure for that, while the last three are > example conversions for the above-mentioned three storage drivers. The > sf.c is the one I need to use in the SPL and have actually tested, > ext4.c and fat.c are included mostly as low-hanging fruit.
Dear Wolfgang Can I ask whether you request changes to this patch series or if my answers to your various comments have been satisfactory? Thanks, Rasmus
