Re: [PATCH v7 2/3] firmware: Rename google firmware directory to coreboot

> Keep the existing CONFIG_GOOGLE_* symbols to avoid user configuration
> churn in this mechanical move.

Is this standard kernel development practice? It seems a bit weird to
me to leave the config symbols mismatching the directory structure and
actual meaning of the setting. How long would we leave them mismatched
like this, forever?

If you want to prevent user config churn, an alternative option would
be to provide the old symbol names as transitional options, like this:

menuconfig COREBOOT_FIRMWARE
  bool "coreboot firmware drivers"
  default n
  ...

if COREBOOT_FIRMWARE

config COREBOOT_CBMEM
  ...

...

endif #COREBOOT_FIRMWARE

# Deprecated symbol names, do not use

menuconfig GOOGLE_FIRMWARE
  bool
  transitional
  select COREBOOT_FIRMWARE

config GOOGLE_CBMEM
  bool
  transitional
  select COREBOOT_CBMEM

...