public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Michal Marek <mmarek@suse.cz>,
	"Yann E. MORIN" <yann.morin.1998@free.fr>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Darren Hart <dvhart@linux.intel.com>,
	linux-kbuild@vger.kernel.org,
	kernel-build-reports@lists.linaro.org,
	Michal Marek <mmarek@suse.com>,
	Thiago Macieira <thiago.macieira@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RFC] Kbuild: avoid "make tinyconfig" warnings
Date: Mon, 4 Jul 2016 12:51:56 -0700	[thread overview]
Message-ID: <20160704195156.GA10164@x> (raw)
In-Reply-To: <20160704142608.2069991-1-arnd@arndb.de>

On Mon, Jul 04, 2016 at 04:25:55PM +0200, Arnd Bergmann wrote:
> The introduction of "make *.config" as a shorthand for merging configuration
> files unfortunately introduced some build warnings that we see in every
> single run of the various build bots testing tinyconfig:
> 
> .config:966:warning: override: NOHIGHMEM changes choice state
> .config:965:warning: override: SLOB changes choice state
> .config:963:warning: override: KERNEL_XZ changes choice state
> .config:962:warning: override: CC_OPTIMIZE_FOR_SIZE changes choice state
> .config:933:warning: override: SLOB changes choice state
> .config:930:warning: override: CC_OPTIMIZE_FOR_SIZE changes choice state
> .config:870:warning: override: SLOB changes choice state
> .config:868:warning: override: KERNEL_XZ changes choice state
> .config:867:warning: override: CC_OPTIMIZE_FOR_SIZE changes choice state
> 
> This changes the behavior for tinyconfig again, so we call the special
> allnoconfig target directly, with the fragment as the KCONFIG_ALLCONFIG
> file so it gets merged into the configuration. The disadvantage of
> this approach is that we cannot pass another KCONFIG_ALLCONFIG on
> the command line, that would again have to be done using the mergeconfig
> script afterwards.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Fixes: 63a91033d52e ("kbuild: add generic mergeconfig target, %.config")
> Link: https://storage.kernelci.org/mainline/v4.7-rc6/x86-tinyconfig/build.log

Thanks for fixing this.
Reviewed-by: Josh Triplett <josh@joshtriplett.org>

As another possibility, which would preserve the ability to use
KCONFIG_ALLCONFIG, what about adding a parameter to mergeconfig to
disable this warning?  I've seen many other uses of mergeconfig in
production systems that have the same problem.

>  scripts/kconfig/Makefile | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/scripts/kconfig/Makefile b/scripts/kconfig/Makefile
> index ebced77deb9c..35d0e191fe3f 100644
> --- a/scripts/kconfig/Makefile
> +++ b/scripts/kconfig/Makefile
> @@ -125,8 +125,8 @@ xenconfig: xen.config
>  	@:
>  
>  PHONY += tinyconfig
> -tinyconfig:
> -	$(Q)$(MAKE) -f $(srctree)/Makefile allnoconfig tiny.config
> +tinyconfig: $(obj)/conf
> +	$(Q)$(MAKE) -f $(srctree)/Makefile allnoconfig KCONFIG_ALLCONFIG=$(wildcard $(srctree)/kernel/configs/tiny.config $(srctree)/arch/$(SRCARCH)/configs/tiny.config)
>  
>  # Help text used by make help
>  help:
> -- 
> 2.9.0
> 

  reply	other threads:[~2016-07-04 19:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04 14:25 [PATCH] [RFC] Kbuild: avoid "make tinyconfig" warnings Arnd Bergmann
2016-07-04 19:51 ` Josh Triplett [this message]
2016-07-04 19:58   ` Josh Triplett
2016-07-06 13:56     ` Arnd Bergmann
2016-07-06 18:32       ` Josh Triplett
2016-07-06 19:58         ` Arnd Bergmann
2016-07-06  2:00 ` Masahiro Yamada
2016-07-06 13:49   ` Arnd Bergmann
2016-07-08  1:41     ` Masahiro Yamada
2016-07-08 11:50       ` Arnd Bergmann

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=20160704195156.GA10164@x \
    --to=josh@joshtriplett.org \
    --cc=arnd@arndb.de \
    --cc=dvhart@linux.intel.com \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.com \
    --cc=mmarek@suse.cz \
    --cc=thiago.macieira@intel.com \
    --cc=yamada.masahiro@socionext.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: 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