From f48acbda7be7074938c06db8ad37705f850661ee Mon Sep 17 00:00:00 2001 From: Martin Roth Date: Fri, 24 Jul 2020 12:24:27 -0600 Subject: 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 Change-Id: I5c37f0ee103721c97483d07a368c0b813e3f25c0 Reviewed-on: https://review.coreboot.org/c/coreboot/+/43824 Tested-by: build bot (Jenkins) Reviewed-by: Aaron Durbin Reviewed-by: Angel Pons --- src/include/mrc_cache.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/include/mrc_cache.h') diff --git a/src/include/mrc_cache.h b/src/include/mrc_cache.h index 5131cbccd2..1cefba9da7 100644 --- a/src/include/mrc_cache.h +++ b/src/include/mrc_cache.h @@ -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 -- cgit v1.2.3