[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241126234813.1602902-1-david.hunter.linux@gmail.com>
Date: Tue, 26 Nov 2024 18:48:13 -0500
From: David Hunter <david.hunter.linux@...il.com>
To: masahiroy@...nel.org
Cc: david.hunter.linux@...il.com,
javier.carrasco.cruz@...il.com,
linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org,
rostedt@...dmis.org,
shuah@...nel.org
Subject: Re: [PATCH v2 2/7] streamline_config.pl: ensure all defaults are tracked
From: david.hunter.linux@...il.com
There are many instances of the second line of a config entry containing infomation about defaults. Here is a summary:
def_bools found: 746
def_tristates found: 59
defaults found: 169
> Can you list some examples of where this happens?
I created a file that finds all the times that a default information is given in the line following a CONFIG entry is created. Here is a link for the output, which will show the file and the line numbers:
https://github.com/dshunter107/linux-tools/blob/main/localmodconfig/defaults.output
If you would like to see the shell script I made to find the locations, you can view it at this link:
https://github.com/dshunter107/linux-tools/blob/main/localmodconfig/check_define.sh
Powered by blists - more mailing lists