Re: commit 0eab62b makes menuconfig more strict regarding the old configs
Patrick Georgi via coreboot <[email protected]>
| Newsgroups | gmane.linux.bios |
|---|---|
| Message-ID | <[email protected]> |
On 28.11.23 19:04, Mike Banon <[email protected]> wrote: > Are there any advantages of KCONFIG_STRICT / KCONFIG_WERROR that > outweigh these potential issues? It ensures that we don't silently build with unknown symbols (typo in manual editing, changes to the config, ...), and wonder why CONFIG_UART_DEBUG=y doesn't actually enable serial output on select Intel chipsets (solution: it was renamed 5 years ago). I put a subset of your question up for discussion[0] earlier today, including a patch that tweaks the behavior to make things pass the *config targets. That should resolve your issue while keeping the safety benefit, no? Patrick [0] https://mail.coreboot.org/hyperkitty/list/[email protected]/thread/M543FU2OIHEMLAFAFAPCFHAD36ISAEKO/ _______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]