public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Andres Salomon <dilinger@queued.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@codemonkey.org.uk>,
	Roland McGrath <roland@redhat.com>,
	Roman Zippel <zippel@linux-m68k.org>
Subject: Re: Additional kconfig targets (cloneconfig, nonint_oldconfig etc)
Date: Wed, 21 May 2008 16:47:03 -0400	[thread overview]
Message-ID: <20080521164703.61c7d715@ephemeral> (raw)
In-Reply-To: <20080502190949.GA30270@uranus.ravnborg.org>

On Fri, 2 May 2008 21:09:49 +0200
Sam Ravnborg <sam@ravnborg.org> wrote:

> With the attached patch you can do:
> 
> make K=my_favourite_config defconfig
> 
> kconfig will read all config values form 'my_favourite_config'
> and set all other symbols to their default value.
> The output is now dense like this:
> # configuration is based on 'my_favourite_config'
> #
> # configuration written to .config
> #
> 


Is this slated for 2.6.27?


> 
> The K= notations works for the usual suspects:
> allnoconfig, allyesconfig, allmodconfig, randconfig and defconfig

Since this is aconf (automated), if we run 'make K=foo defconfig' and
'foo' doesn't contain one of the necessary values.. the build will fail,
right?

[...]
> 
> What is missing:
> 1) No support for .gz input file
>    But aconf.sh should be easy to adjust to this
> 
> 2) We hardcode that files name *_defconfig are found
>    in arch/$ARCH/configs/*
> 
> 3) Implement newsymbolsconfig (any better name?)
>    Shall list all new symbols and shall not write
>    any config
> 

I'm not sure I see the point of #3.

  reply	other threads:[~2008-05-21 20:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29 18:35 Additional kconfig targets (cloneconfig, nonint_oldconfig etc) Sam Ravnborg
2008-04-29 21:24 ` Andres Salomon
2008-04-30  6:35   ` Sam Ravnborg
2008-04-30 14:43     ` Jan Engelhardt
2008-04-30 10:45   ` SL Baur
2008-04-30 15:01     ` Randy Dunlap
2008-04-30 20:32       ` SL Baur
2008-04-30 20:35         ` Roland McGrath
2008-04-30 20:37         ` Sam Ravnborg
2008-04-30 14:44 ` Jan Engelhardt
2008-05-02 10:56   ` Sam Ravnborg
2008-05-01  4:40 ` Roman Zippel
2008-05-01  6:12   ` Sam Ravnborg
2008-05-03 21:49   ` Sam Ravnborg
2008-05-02 19:09 ` Sam Ravnborg
2008-05-21 20:47   ` Andres Salomon [this message]
2008-05-21 21:11     ` Dave Jones
2008-05-21 21:38       ` Andres Salomon
2008-05-22 19:06       ` Alexey Dobriyan
2008-05-21 21:47     ` Sam Ravnborg
2008-06-13 18:10       ` Andres Salomon
2008-06-13 18:14         ` Sam Ravnborg

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=20080521164703.61c7d715@ephemeral \
    --to=dilinger@queued.net \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.com \
    --cc=sam@ravnborg.org \
    --cc=zippel@linux-m68k.org \
    /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