From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: masahiroy@kernel.org, jeremie.francois@gmail.com,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] scripts : config : Added example use when run without argument,extend help
Date: Fri, 11 Sep 2020 04:29:28 +0530 [thread overview]
Message-ID: <20200910225928.GB10714@Gentoo> (raw)
In-Reply-To: <13084d55-6b9a-5c6b-0ce0-84739b3e1072@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1881 bytes --]
On 15:52 Thu 10 Sep 2020, Randy Dunlap wrote:
>Hi,
>
>Please be more careful. There are many errors here. (see below)
Silly me! thanks Randy :)
~Bhaskar
>
>On 9/10/20 4:07 AM, Bhaskar Chowdhury wrote:
>> This patch extends the help section by adding an explicit example of use.
>>
>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>> ---
>> scripts/config | 19 +++++++++++++++++++
>> 1 file changed, 19 insertions(+)
>>
>> diff --git a/scripts/config b/scripts/config
>> index eee5b7f3a092..b75a5aab2453 100755
>> --- a/scripts/config
>> +++ b/scripts/config
>> @@ -45,6 +45,25 @@ make time.
>> By default, $myname will upper-case the given symbol. Use --keep-case to keep
>> the case of all following symbols unchanged.
>>
>> +The concerete example, say, you want to change any particular config ,like
>
> concrete config, like
>
>> +GKOV for profiling , you can simply use this command
>
> GCOV
>
>> +
>> +To enable :
>
> enable:
>
>> +
>> +#scripts/config --enable GKOV_KERNEL && grep GKOV .config
>
> GCOV_KERNEL GCOV
>
>> +
>> + and the output will be like this :
>
> this:
>
>> +
>> + CONFIG_GKOV_KERNEL=y
>
> GCOV
>
>> +
>> +To disable :
>
> disable:
>
>> +
>> +#scripts/config --disable GKOV_KERNEL && grep GKOV .config
>
> GCOV GCOV
>
>> +
>> + and the output will be like this :
>
> this:
>
>> +
>> +# CONFIG_GKOV_KERNEL is not set
>
> GCOV
>
>> +
>> $myname uses 'CONFIG_' as the default symbol prefix. Set the environment
>> variable CONFIG_ to the prefix to use. Eg.: CONFIG_="FOO_" $myname ...
>> EOL
>>
>
>
>--
>~Randy
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-09-10 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 11:07 [PATCH] scripts : config : Added example use when run without argument,extend help Bhaskar Chowdhury
2020-09-10 22:52 ` Randy Dunlap
2020-09-10 22:59 ` Bhaskar Chowdhury [this message]
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=20200910225928.GB10714@Gentoo \
--to=unixbhaskar@gmail.com \
--cc=jeremie.francois@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=rdunlap@infradead.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