src: Change BOOL CONFIG_ to CONFIG() in comments & strings
The Kconfig lint tool checks for cases of the code using BOOL type Kconfig options directly instead of with CONFIG() and will print out warnings about it. It gets confused by these references in comments and strings. To fix it so that it can find the real issues, just update these as we would with real issues. Signed-off-by: Martin Roth <martin@coreboot.org> Change-Id: I5c37f0ee103721c97483d07a368c0b813e3f25c0 Reviewed-on: https://review.coreboot.org/c/coreboot/+/43824 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Reviewed-by: Angel Pons <th3fanbus@gmail.com>
This commit is contained in:
committed by
Patrick Georgi
parent
af56a77915
commit
f48acbda7b
@@ -14,7 +14,7 @@ enum {
|
||||
|
||||
/*
|
||||
* It's up to the caller to decide when to retrieve and stash data. There is
|
||||
* differentiation on recovery mode CONFIG_HAS_RECOVERY_MRC_CACHE, but that's
|
||||
* differentiation on recovery mode CONFIG(HAS_RECOVERY_MRC_CACHE), but that's
|
||||
* only for locating where to retrieve and save the data. If a platform doesn't
|
||||
* want to update the data then it shouldn't stash the data for saving.
|
||||
* Similarly, if the platform doesn't need the data for booting because of a
|
||||
|
||||
Reference in New Issue
Block a user