public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	uclinux-h8-devel@lists.sourceforge.jp
Subject: Re: [PATCH] arch/h8300: add a defconfig target
Date: Fri, 20 Jul 2018 09:15:58 +0900	[thread overview]
Message-ID: <87in5arcch.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <84ff16cd-2549-56f2-9e26-60b70188c9f2@infradead.org>

On Thu, 19 Jul 2018 15:04:29 +0900,
Randy Dunlap wrote:
> 
> From: Randy Dunlap <rdunlap@infradead.org>
> 
> Make the "defconfig" target valid for arch/h8300.  Currently
> "make ARCH=h8300 defconfig" produces:
> 
> *** Can't find default configuration "arch/h8300/defconfig"!
> ../scripts/kconfig/Makefile:87: recipe for target 'defconfig' failed
> 
> By adding a value for KBUILD_DEFCONFIG, "make ARCH=h8300 defconfig"
> successfully produces a kernel .config file:
> 
> *** Default configuration is based on 'edosk2674_defconfig'
> 
> This is useful for Kconfig editing/testing.
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
> Cc: uclinux-h8-devel@lists.sourceforge.jp (moderated for non-subscribers)
> ---
>  arch/h8300/Makefile |    2 ++
>  1 file changed, 2 insertions(+)
> 
> --- linux-next-20180717.orig/arch/h8300/Makefile
> +++ linux-next-20180717/arch/h8300/Makefile
> @@ -8,6 +8,8 @@
>  # (C) Copyright 2002-2015 Yoshinori Sato <ysato@users.sourceforge.jp>
>  #
>  
> +KBUILD_DEFCONFIG := edosk2674_defconfig
> +
>  cflags-$(CONFIG_CPU_H8300H)	:= -mh
>  aflags-$(CONFIG_CPU_H8300H)	:= -mh -Wa,--mach=h8300h
>  ldflags-$(CONFIG_CPU_H8300H)	:= -mh8300helf_linux
> 
> 

Applied for h8300-next.
Thanks.

-- 
Yosinori Sato

      reply	other threads:[~2018-07-20  0:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19  6:04 [PATCH] arch/h8300: add a defconfig target Randy Dunlap
2018-07-20  0:15 ` Yoshinori Sato [this message]

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=87in5arcch.wl-ysato@users.sourceforge.jp \
    --to=ysato@users.sourceforge.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=uclinux-h8-devel@lists.sourceforge.jp \
    /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