Skip to content

Introduce initial versions of new Command Config files.

Jon Loeliger u-boot 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 19 patches 0 repliesNew

Patches in v1 No applies recorded yet

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

Reviews trailers per patch

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

Read the v1 thread

Cover letter [U-Boot-Users] [PATCH: cmdcfg: 00/19] Introduce initial versions of new Command Config files.

So, like, the other day Wolfgang Denk mumbled:

Quoted 9 lines
Quoted 7 lines · In message <[email protected]> you wrote:

#ifdef CONFIG_CMD_AUTOSCRIPT
#undef CONFIG_CMD_AUTOSCRIPT
#define CONFIG_CMD_AUTOSCRIPT CONFIG_CMD_AUTOSCRIPT #else
#define CONFIG_CMD_AUTOSCRIPT 0
#endif

Quoted 5 lines

#define foo foo ??? Not that looks uterly strange to me...

Quoted 1 line

... ( repeat for each CONFIG_CMD_x )

grrrghh....

I agree.

Quoted 5 lines
Quoted 2 lines

With this technique, you won't need to modify all of the source files that use CONFIG_COMMANDS.

But we *do* want to modify all files to move them to using the new scheme.

And my follow up patch will series do it again too!

Thanks,
jdl