kconfig: do not warn about modules built in
The streamline_config.pl finds all the configs that are needed to compile the currently loaded modules. After it creates the .config file, it tests to make sure all the configs that are needed were set. It only looks at the configs that are modules, it does not look at the builtin configs. This causes unnecessary warnings about modules not being covered. Reported-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
This commit is contained in:
parent
74398d3224
commit
ea2c1894b6
1 changed files with 5 additions and 3 deletions
|
@ -256,12 +256,14 @@ my %setconfigs;
|
|||
# Finally, read the .config file and turn off any module enabled that
|
||||
# we could not find a reason to keep enabled.
|
||||
while(<CIN>) {
|
||||
if (/^(CONFIG.*)=m/) {
|
||||
if (/^(CONFIG.*)=(m|y)/) {
|
||||
if (defined($configs{$1})) {
|
||||
$setconfigs{$1} = 1;
|
||||
$setconfigs{$1} = $2;
|
||||
print;
|
||||
} else {
|
||||
} elsif ($2 eq "m") {
|
||||
print "# $1 is not set\n";
|
||||
} else {
|
||||
print;
|
||||
}
|
||||
} else {
|
||||
print;
|
||||
|
|
Loading…
Reference in a new issue