From: Michael Ellerman <mpe@ellerman.id.au> To: <linuxppc-dev@ozlabs.org> Cc: <linux-kernel@vger.kernel.org>, linux-kbuild@vger.kernel.org, yann.morin.1998@free.fr, mmarek@suse.com Subject: [RFC PATCH 2/2] powerpc: Add ppc64le_defconfig Date: Wed, 23 Sep 2015 15:40:35 +1000 [thread overview] Message-ID: <1442986835-13985-2-git-send-email-mpe@ellerman.id.au> (raw) In-Reply-To: <1442986835-13985-1-git-send-email-mpe@ellerman.id.au> Based directly on ppc64_defconfig using merge_config. Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> --- arch/powerpc/Makefile | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/arch/powerpc/Makefile b/arch/powerpc/Makefile index b9b4af2af9a5..3704db45a832 100644 --- a/arch/powerpc/Makefile +++ b/arch/powerpc/Makefile @@ -288,6 +288,10 @@ PHONY += pseries_le_defconfig pseries_le_defconfig: $(call merge_into_defconfig,pseries_defconfig,le) +PHONY += ppc64le_defconfig +ppc64le_defconfig: + $(call merge_into_defconfig,ppc64_defconfig,le) + PHONY += mpc85xx_defconfig mpc85xx_defconfig: $(call merge_into_defconfig,mpc85xx_basic_defconfig,\ -- 2.1.4
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au> To: linuxppc-dev@ozlabs.org Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org, yann.morin.1998@free.fr, mmarek@suse.com Subject: [RFC PATCH 2/2] powerpc: Add ppc64le_defconfig Date: Wed, 23 Sep 2015 15:40:35 +1000 [thread overview] Message-ID: <1442986835-13985-2-git-send-email-mpe@ellerman.id.au> (raw) In-Reply-To: <1442986835-13985-1-git-send-email-mpe@ellerman.id.au> Based directly on ppc64_defconfig using merge_config. Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> --- arch/powerpc/Makefile | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/arch/powerpc/Makefile b/arch/powerpc/Makefile index b9b4af2af9a5..3704db45a832 100644 --- a/arch/powerpc/Makefile +++ b/arch/powerpc/Makefile @@ -288,6 +288,10 @@ PHONY += pseries_le_defconfig pseries_le_defconfig: $(call merge_into_defconfig,pseries_defconfig,le) +PHONY += ppc64le_defconfig +ppc64le_defconfig: + $(call merge_into_defconfig,ppc64_defconfig,le) + PHONY += mpc85xx_defconfig mpc85xx_defconfig: $(call merge_into_defconfig,mpc85xx_basic_defconfig,\ -- 2.1.4
next prev parent reply other threads:[~2015-09-23 5:41 UTC|newest] Thread overview: 19+ 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 ` Michael Ellerman 2015-09-23 5:40 ` Michael Ellerman [this message] 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-10-02 7:47 ` Michael Ellerman 2015-09-23 9:50 ` [RFC PATCH 1/2] scripts/kconfig/Makefile: Allow KBUILD_DEFCONFIG to be a target Michal Marek 2015-09-23 22:16 ` 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-02 7:47 ` 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=1442986835-13985-2-git-send-email-mpe@ellerman.id.au \ --to=mpe@ellerman.id.au \ --cc=linux-kbuild@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxppc-dev@ozlabs.org \ --cc=mmarek@suse.com \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.