Martin Roth has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/31773 )
Change subject: Add new CONFIG(XXX) macro to replace IS_ENABLED(CONFIG_XXX) ......................................................................
Patch Set 2:
Since IS_ENABLED is still supported, it's not really disruptive. With the other changes it's now a lint warning. After the next release (late April I guess) we can make it a lint error. That way only branches older than two months will run into it.
I'm talking about merging patches from master into other branches. The change will have to be applied to any branch that's still being patched from coreboot or new patches that include the new macro won't apply cleanly.
The patch to change the macros will have to be re-created for each remote branch using the command in the next commit because that patch won't apply cleanly.
Once the change is applied to a branch, any patch from before the change that includes IS_ENABLED will no longer apply cleanly.
As I said, it's a LITTLE disruptive just because it's so broad.