From: Darren Hart <dvhart@linux.intel.com>
To: John Stultz <john.stultz@linaro.org>
Cc: linux-kbuild@vger.kernel.org, Michal Marek <mmarek@suse.cz>,
Bruce.Ashfield@windriver.com
Subject: Re: [PATCH 2/2] merge_config.sh: Add option to display redundant configs
Date: Thu, 22 Mar 2012 20:45:29 -0700 [thread overview]
Message-ID: <4F6BF1D9.107@linux.intel.com> (raw)
In-Reply-To: <1332453949-5872-3-git-send-email-john.stultz@linaro.org>
A few spelling nitpics :-)
On 03/22/2012 03:05 PM, John Stultz wrote:
> Provide a -r option to display when fragments contain reundent
s/reundent/redundant/
> options
>
> CC: Michal Marek <mmarek@suse.cz>
> CC: Bruce.Ashfield@windriver.com
> CC: Darren Hart <dvhart@linux.intel.com>
> Signed-off-by: John Stultz <john.stultz@linaro.org>
> ---
> scripts/kconfig/merge_config.sh | 11 +++++++++++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/scripts/kconfig/merge_config.sh b/scripts/kconfig/merge_config.sh
> index ceadf0e..d92edc3 100755
> --- a/scripts/kconfig/merge_config.sh
> +++ b/scripts/kconfig/merge_config.sh
> @@ -31,10 +31,12 @@ usage() {
> echo " -h display this help text"
> echo " -m only merge the fragments, do not execute the make command"
> echo " -n use allnoconfig instead of alldefconfig"
> + echo " -r list redundant enteries when merging fragments"
s/enteries/entries/
> }
>
> MAKE=true
> ALLTARGET=alldefconfig
> +WARNREDUN=false
>
> while true; do
> case $1 in
> @@ -52,6 +54,11 @@ while true; do
> usage
> exit
> ;;
> + "-r")
> + WARNREDUN=true
> + shift
> + continue
> + ;;
> *)
> break
> ;;
> @@ -79,6 +86,10 @@ for MERGE_FILE in $MERGE_LIST ; do
> echo Previous value: $PREV_VAL
> echo New value: $NEW_VAL
> echo
> + else
Can this just be an elif and avoid the nested if block?
> + if [ "$WARNREDUN" = "true" ]; then
> + echo Value of $CFG is redundant by fragment $MERGE_FILE:
> + fi
No indentation... is that just my MUA?
> fi
> sed -i "/$CFG[ =]/d" $TMP_FILE
> fi
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-03-23 3:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 22:05 [PATCH 0/2] merge_config.sh updates for 3.4? John Stultz
2012-03-22 22:05 ` [PATCH 1/2] merge_config.sh: Set execute bit John Stultz
2012-03-23 3:45 ` Darren Hart
2012-03-23 12:58 ` Bruce Ashfield
2012-03-30 13:16 ` Michal Marek
2012-03-22 22:05 ` [PATCH 2/2] merge_config.sh: Add option to display redundant configs John Stultz
2012-03-23 3:45 ` Darren Hart [this message]
2012-03-23 19:52 ` John Stultz
2012-03-23 13:02 ` Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2012-03-23 19:52 John Stultz
2012-03-23 20:24 ` Darren Hart
2012-03-30 13:14 ` Michal Marek
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=4F6BF1D9.107@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=Bruce.Ashfield@windriver.com \
--cc=john.stultz@linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
/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