diff options
| author | Steven Rostedt <[email protected]> | 2022-12-02 11:59:36 -0500 |
|---|---|---|
| committer | Steven Rostedt (Google) <[email protected]> | 2022-12-07 20:36:16 -0500 |
| commit | ef784eebb56425eed6e9b16e7d47e5c00dcf9c38 (patch) | |
| tree | a59399b99c68d8d86b844d039a2d7111ccc1f88a /lib/memory-notifier-error-inject.c | |
| parent | 76dcd734eca23168cb008912c0f69ff408905235 (diff) | |
ktest.pl minconfig: Unset configs instead of just removing them
After a full run of a make_min_config test, I noticed there were a lot of
CONFIGs still enabled that really should not be. Looking at them, I
noticed they were all defined as "default y". The issue is that the test
simple removes the config and re-runs make oldconfig, which enables it
again because it is set to default 'y'. Instead, explicitly disable the
config with writing "# CONFIG_FOO is not set" to the file to keep it from
being set again.
With this change, one of my box's minconfigs went from 768 configs set,
down to 521 configs set.
Link: https://lkml.kernel.org/r/[email protected]
Cc: [email protected]
Fixes: 0a05c769a9de5 ("ktest: Added config_bisect test type")
Reviewed-by: John 'Warthog9' Hawley (VMware) <[email protected]>
Signed-off-by: Steven Rostedt (Google) <[email protected]>
Diffstat (limited to 'lib/memory-notifier-error-inject.c')
0 files changed, 0 insertions, 0 deletions