From: Michal Marek <mmarek@suse.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
yann.morin.1998@free.fr
Subject: Re: [RFC PATCH 1/2] scripts/kconfig/Makefile: Allow KBUILD_DEFCONFIG to be a target
Date: Wed, 23 Sep 2015 11:50:52 +0200 [thread overview]
Message-ID: <560275FC.60104@suse.com> (raw)
In-Reply-To: <1442986835-13985-1-git-send-email-mpe@ellerman.id.au>
On 2015-09-23 07:40, Michael Ellerman wrote:
> +else ifneq ($(wildcard arch/$(SRCARCH)/configs/$(KBUILD_DEFCONFIG)),)
> @$(kecho) "*** Default configuration is based on '$(KBUILD_DEFCONFIG)'"
> $(Q)$< $(silent) --defconfig=arch/$(SRCARCH)/configs/$(KBUILD_DEFCONFIG) $(Kconfig)
> +else
> + @$(kecho) "*** Default configuration is based on target '$(KBUILD_DEFCONFIG)'"
> + $(Q)$(MAKE) -f $(srctree)/Makefile $(KBUILD_DEFCONFIG)
> endif
What is the anticipated usage of this? The patch is not needed to make
make ppc64le_defconfig
work with the second patch. If it was, this would create a loop anyway.
Michal
next prev parent reply other threads:[~2015-09-23 9:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 5:40 [RFC PATCH 1/2] scripts/kconfig/Makefile: Allow KBUILD_DEFCONFIG to be a target Michael Ellerman
2015-09-23 5:40 ` [RFC PATCH 2/2] powerpc: Add ppc64le_defconfig Michael Ellerman
2015-10-02 7:47 ` [RFC,2/2] " Michael Ellerman
2015-09-23 9:50 ` Michal Marek [this message]
2015-09-23 22:16 ` [RFC PATCH 1/2] scripts/kconfig/Makefile: Allow KBUILD_DEFCONFIG to be a target Michael Ellerman
2015-09-25 20:46 ` Michal Marek
2015-10-01 6:14 ` Michael Ellerman
2015-10-01 6:50 ` Michal Marek
2015-10-01 7:05 ` Michael Ellerman
2015-10-02 7:47 ` [RFC, " Michael Ellerman
2015-10-13 21:02 ` Olof Johansson
2015-10-13 23:43 ` Michael Ellerman
2015-10-14 16:54 ` Olof Johansson
2015-10-15 3:27 ` Michael Ellerman
2015-10-15 7:34 ` 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=560275FC.60104@suse.com \
--to=mmarek@suse.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=yann.morin.1998@free.fr \
/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).