linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Gabriel de Perthuis <g2p.code@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 1/2] kconfig/merge_config.sh: Support KCONFIG_CONFIG
Date: Wed, 14 Oct 2015 16:11:20 +0200	[thread overview]
Message-ID: <561E6288.6000808@suse.cz> (raw)
In-Reply-To: <561E5DA2.6020405@gmail.com>

On 2015-10-14 15:50, Gabriel de Perthuis wrote:
> Le 14/10/2015 à 12:56, Michal Marek a écrit :
>> On 2015-09-09 19:33, Gabriel de Perthuis wrote:
>>> All make targets support $KCONFIG_CONFIG because they
>>> run scripts/kconf.  Make sure merge_config.sh accesses the
>>> correct file in all cases.
>>>
>>> Previously this script broke in two different code paths,
>>> one for targets like kvmconfig (which use merge_config.sh -m
>>> then call a target that respects KCONFIG_CONFIG) and one for
>>> direct use of the script without -m, which called make rules
>>> that edit KCONFIG_CONFIG but verified a different file.
>>>
>>> Signed-off-by: Gabriel de Perthuis <g2p.code@gmail.com>
>>> Cc: Michal Marek <mmarek@suse.cz>
>>> ---
>>>    scripts/kconfig/merge_config.sh | 6 +++---
>>>    1 file changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/scripts/kconfig/merge_config.sh
>>> b/scripts/kconfig/merge_config.sh
>>> index 0d883b3..5f1e110 100755
>>> --- a/scripts/kconfig/merge_config.sh
>>> +++ b/scripts/kconfig/merge_config.sh
>>> @@ -122,13 +122,13 @@ for MERGE_FILE in $MERGE_LIST ; do
>>>    	done
>>>    	cat $MERGE_FILE >> $TMP_FILE
>>>    done
>>>     if [ "$RUNMAKE" = "false" ]; then
>>> -	cp $TMP_FILE $OUTPUT/.config
>>> +	cp $TMP_FILE ${KCONFIG_CONFIG:=$OUTPUT/.config}
>>>    	echo "#"
>>> -	echo "# merged configuration written to $OUTPUT/.config (needs make)"
>>> +	echo "# merged configuration written to $KCONFIG_CONFIG (needs make)"
>>
>> The message will not contain the name of the output file when invoked
>> directly and without the variable set.
> 
> Don't miss the ${:=} assignments.

Ah, you are right. I confused them with ":-".


>  > Also, it will be more readable if you set the default value once and 
> then use simply $KCONFIG_CONFIG.
> 
> I'll resubmit something more explicit, pick whichever you prefer.

Please do so. While the patch is correct, patching the first usage of
the variable in various code flows is not easy to follow.

Michal

  reply	other threads:[~2015-10-14 14:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09 17:33 [PATCH 1/2] kconfig/merge_config.sh: Support KCONFIG_CONFIG Gabriel de Perthuis
2015-10-14 10:56 ` Michal Marek
2015-10-14 13:50   ` Gabriel de Perthuis
2015-10-14 14:11     ` Michal Marek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-10-14 13:57 Gabriel de Perthuis
2015-10-14 14:19 ` 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=561E6288.6000808@suse.cz \
    --to=mmarek@suse.cz \
    --cc=g2p.code@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).