Skip to content

env: handle special variables and selective env default

Marek Vasut u-boot 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v4 Latest0 of 7 patches 0 repliesNew

Patches in v4 No applies recorded yet

None of the 7 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v4 yet.

Read the v4 thread

Cover letter [U-Boot] [PATCH v4 0/7] env: handle special variables and selective env default

Dear Wolfgang Denk,

Quoted 3 lines

Dear Gerlando Falauto,

In message <[email protected]>

Quoted 26 lines · you
Quoted 26 lines

This patchset modifies the handling of all the operations on the environment (set/import/default) so to unify handling of special variables.
On top of that we implement a selective "env default".

A selective "env import" would imply a user API change and should therefore be discussed separately.

NOTE:
The entire patchset generates an increase in code size of about 1200 bytes on a PowerPC target.
As much as I would like to get rid of the set_default_vars() function in env_common.c, I have not found a nice way to do so.

Changes in the syntax (user API):
- "env default" -f: override write-once variables, -a means all
- display a warning when trying to set to default variables not

present in the default env.

Changes from v3:
- rebased to current trunk (was not compilable)
- removed compiler warnings
- added an independent cosmetic patch on top of the series (from which only

Quoted 6 lines
Quoted 1 line

a later patch would actually benefit)

In which way are these changes related to the code I checked in for testing into the "env" branch?

Is this patch series supposed to replace this stuff?

Yes, looks to me that way

Quoted 4 lines

Best regards,

Wolfgang Denk

Best regards,
Marek Vasut

Read the cover letter in its thread