From: David Hunter <david.hunter.linux@gmail.com>
To: masahiroy@kernel.org
Cc: david.hunter.linux@gmail.com, javier.carrasco.cruz@gmail.com,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
rostedt@goodmis.org, shuah@kernel.org
Subject: Re: [PATCH v2 2/7] streamline_config.pl: ensure all defaults are tracked
Date: Tue, 26 Nov 2024 18:48:13 -0500 [thread overview]
Message-ID: <20241126234813.1602902-1-david.hunter.linux@gmail.com> (raw)
In-Reply-To: <CAK7LNAR8TQx=r-esfi+dJ3=TQ+6Om+LPadhDPqn3TLH93xi4WQ@mail.gmail.com>
From: david.hunter.linux@gmail.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
next prev parent reply other threads:[~2024-11-26 23:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 14:13 [PATCH v3 0/7] streamline_config.pl: fix: process configs set to "y" David Hunter
2024-10-14 14:13 ` [PATCH v2 1/7] streamline_config.pl: fix missing variable operator in debug print David Hunter
2024-11-05 23:05 ` Masahiro Yamada
2024-10-14 14:13 ` [PATCH v2 2/7] streamline_config.pl: ensure all defaults are tracked David Hunter
2024-10-15 23:09 ` Steven Rostedt
2024-11-05 23:05 ` Masahiro Yamada
2024-11-26 23:48 ` David Hunter [this message]
2024-11-27 1:09 ` Steven Rostedt
2024-11-05 23:05 ` Masahiro Yamada
2024-10-14 14:13 ` [PATCH v2 3/7] streamline_config.pl: remove prompt warnings for configs with defaults David Hunter
2024-11-05 23:13 ` Masahiro Yamada
2024-10-14 14:13 ` [PATCH v1 4/7] streamline_config.pl: include tool to learn about a config option David Hunter
2024-11-05 23:15 ` Masahiro Yamada
2024-10-14 14:13 ` [PATCH v2 5/7] streamline_config.pl: fix: implement choice for kconfigs David Hunter
2024-10-17 22:32 ` Steven Rostedt
2024-11-05 23:33 ` Masahiro Yamada
2024-11-27 13:18 ` David Hunter
2024-11-30 9:41 ` Masahiro Yamada
2024-10-14 14:13 ` [PATCH v2 6/7] streamline_config.pl: process config options set to "y" David Hunter
2024-10-15 23:20 ` Steven Rostedt
2024-11-05 23:44 ` Masahiro Yamada
2024-10-14 14:13 ` [PATCH v2 7/7] streamline_config.pl: check prompt for bool options David Hunter
2024-11-05 23:45 ` Masahiro Yamada
2024-11-27 13:26 ` David Hunter
2024-11-27 22:50 ` Masahiro Yamada
2024-11-28 15:04 ` David Hunter
2024-10-17 22:37 ` [PATCH v3 0/7] streamline_config.pl: fix: process configs set to "y" Steven Rostedt
2024-10-18 14:30 ` Steven Rostedt
2024-11-27 23:05 ` David Hunter
2024-11-27 23:26 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241126234813.1602902-1-david.hunter.linux@gmail.com \
--to=david.hunter.linux@gmail.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox