From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from metis.ext.pengutronix.de ([2001:6f8:1178:4:290:27ff:fe1d:cc33]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1YAwRd-0001XG-Fj for barebox@lists.infradead.org; Tue, 13 Jan 2015 08:03:22 +0000 Date: Tue, 13 Jan 2015 09:02:58 +0100 From: Sascha Hauer Message-ID: <20150113080258.GX23940@pengutronix.de> References: <1421131570-7450-1-git-send-email-yamada.m@jp.panasonic.com> <29573FD6-1527-4C63-ACBE-85847B0F1277@jcrosoft.com> <20150113165447.CACE.AA925319@jp.panasonic.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20150113165447.CACE.AA925319@jp.panasonic.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: [PATCH] kbuild: add KBUILD_DEFCONFIG To: Masahiro Yamada Cc: barebox@lists.infradead.org On Tue, Jan 13, 2015 at 04:54:47PM +0900, Masahiro Yamada wrote: > Hi Jean-Christophe, > > On Tue, 13 Jan 2015 14:53:19 +0800 > Jean-Christophe PLAGNIOL-VILLARD wrote: > > > > > > On Jan 13, 2015, at 2:46 PM, Masahiro Yamada wrote: > > > > > > This allows "make ARCH=... defconfig". > > > > > > Fox example, you can type "make defconfig" instead of > > > "make sandbox_defconfig". > > > > > > Signed-off-by: Masahiro Yamada > > > --- > > > > > > arch/arm/Makefile | 1 + > > > arch/blackfin/Makefile | 1 + > > > arch/efi/Makefile | 2 ++ > > > arch/nios2/Makefile | 2 ++ > > > arch/openrisc/Makefile | 2 ++ > > > arch/sandbox/Makefile | 1 + > > > arch/x86/Makefile | 2 ++ > > > 7 files changed, 11 insertions(+) > > > > > > diff --git a/arch/arm/Makefile b/arch/arm/Makefile > > > index f06e2a0..9dd983b 100644 > > > --- a/arch/arm/Makefile > > > +++ b/arch/arm/Makefile > > > @@ -1,3 +1,4 @@ > > > +KBUILD_DEFCONFIG := versatilepb_defconfig > > > > no sure we need a default config on arm and some other > > > > I known we use them on the kernel but here it could result in a broken board > > if use not carefully > > > > for arch that only have 1 defconfig and will only have one maybe > > > > Why could it result in a broken board? (It seems harmless to me.) > > I think it is useful at least for Sandbox and some other arches that > have only "generic_defconfig". > > It is true that KBUILD_DEFCONFIG is not so useful for ARM. > If it is not desired for ARM (and Blackfin), we can drop it, of course. I think it makes sense on EFI, x86 and sandbox. On the other architectures one must know which board to build, so let's do not get others the impression that the generic defconfig produces something useful. This also includes nios2 and openrisc. For these two only one defconfig exists but I think this is more because these architectures have very limited usage. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox