UPSTREAM: Kconfig: Update default hex values to start with 0x
Kconfig hex values don't need to be in quotes, and should start with '0x'. If the default value isn't set this way, Kconfig will add the 0x to the start, and the entry can be added unnecessarily to the defconfig since it's "different" than what was set by the default. A check for this has been added to the Kconfig lint tool. BUG=None BRANCH=None TEST=None Signed-off-by: Martin Roth <martinroth@google.com> Reviewed-on: https://review.coreboot.org/16834 Tested-by: build bot (Jenkins) Reviewed-by: Kysti Mlkki <kyosti.malkki@gmail.com> Change-Id: I86f37340682771700011b6285e4b4af41b7e9968 Reviewed-on: https://chromium-review.googlesource.com/391938 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org>
This commit is contained in:
parent
4347faae05
commit
306a033bfb
28 changed files with 35 additions and 35 deletions
|
|
@ -72,7 +72,7 @@ config EC_GOOGLE_CHROMEEC_SPI_WAKEUP_DELAY_US
|
|||
config EC_GOOGLE_CHROMEEC_SPI_CHIP
|
||||
depends on EC_GOOGLE_CHROMEEC_SPI
|
||||
hex
|
||||
default 0
|
||||
default 0x0
|
||||
|
||||
config EC_EXTERNAL_FIRMWARE
|
||||
depends on EC_GOOGLE_CHROMEEC
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue