From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>, masahiroy@kernel.org
Cc: jeremie.francois@gmail.com, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH V2] scripts : config : Added example use when run without argument,extend help
Date: Thu, 10 Sep 2020 20:08:36 -0700 [thread overview]
Message-ID: <508f3917-8b3f-fe38-f6bf-43f5026fc4e2@infradead.org> (raw)
In-Reply-To: <20200911015421.22193-1-unixbhaskar@gmail.com>
On 9/10/20 6:54 PM, Bhaskar Chowdhury wrote:
> This patch extends the help section by adding an explicit example of use.
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
Difference between versions goes here.
> scripts/config | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/scripts/config b/scripts/config
> index eee5b7f3a092..d905dccabb94 100755
> --- a/scripts/config
> +++ b/scripts/config
> @@ -45,6 +45,23 @@ make time.
> By default, $myname will upper-case the given symbol. Use --keep-case to keep
> the case of all following symbols unchanged.
>
> +The concrete example, say, you want to change any particular config,like
config, like
> +GCOV for profiling, you can simply use this command
command.
> +
> +To enable:
> +
> +#scripts/config --enable GCOV_KERNEL && grep GCOV .config
> +
> + and the output will be like this:
> +
> + CONFIG_GCOV_KERNEL=y
> +
> +To disable:
> +
> +#scripts/config --disable GCOV_KERNEL && grep GCOV .config
> +
> +# CONFIG_GCOV_KERNEL is not set
> +
> $myname uses 'CONFIG_' as the default symbol prefix. Set the environment
> variable CONFIG_ to the prefix to use. Eg.: CONFIG_="FOO_" $myname ...
> EOL
>
I don't know why we need this extra help text.
--
~Randy
next prev parent reply other threads:[~2020-09-11 3:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 1:54 Bhaskar Chowdhury
2020-09-11 3:08 ` Randy Dunlap [this message]
2020-09-11 3:40 ` Bhaskar Chowdhury
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=508f3917-8b3f-fe38-f6bf-43f5026fc4e2@infradead.org \
--to=rdunlap@infradead.org \
--cc=jeremie.francois@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=unixbhaskar@gmail.com \
/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
all inboxes | Powered by JetHome®