Closed Jochen-Kall closed 3 years ago
@Jochen-Kall disabling a config is usually done with the line # CONFIG_FOO is not set
as you can see in an example at https://git.yoctoproject.org/cgit/cgit.cgi/yocto-kernel-cache/tree/cfg/x86_64.cfg#n9
@Jochen-Kall disabling a config is usually done with the line
# CONFIG_FOO is not set
as you can see in an example at https://git.yoctoproject.org/cgit/cgit.cgi/yocto-kernel-cache/tree/cfg/x86_64.cfg#n9
Thanks Sudip, meant to ask about that, but forgot. Is this a matter of convention, or is there an actual functional difference? In any case, I'll fix it.
Switched off all formerly enabled tristate configs, that lead to an unloaded module if set to "m"