[PATCH v3] env: spi: Fix gd->env_valid for the first write

[Tom Rini]

On Mon, 22 Sep 2025 18:03:39 +0200, Michal Simek wrote:

> When both SPI environment locations are invalid (gd->env_valid ==
> ENV_INVALID), the first call to saveenv writes to the primary location and
> sets the active flag. However, the logic for updating gd->env_valid
> incorrectly sets it to ENV_REDUND, which does not match the actual location
> written. This causes the first two writes to target the same location, and
> alternation only begins after the second write.
> 
> [...]

Applied to u-boot/next, thanks!

[1/1] env: spi: Fix gd->env_valid for the first write
      commit: e589d5822cac10915ec04e8d9044d2460aec8924
-- 
Tom