All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Roland Dreier <rdreier@cisco.com>,
	Christoph Hellwig <hch@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] replace "make ARCH=i386/x86_64 with make ARCH=x86"
Date: Mon, 05 Nov 2007 17:33:08 -0800	[thread overview]
Message-ID: <472FC454.4040701@zytor.com> (raw)
In-Reply-To: <20071106012916.GE3444@stusta.de>

Adrian Bunk wrote:
>>
>> The issue with "make allyesconfig" concerns me, although the same situation 
>> already exists with any multiple-choice configuration.  What I guess we 
>> really want is to be able to specify a few specific choices.
> 
> It's already available:
> 
> $ cat myconfig
> CONFIG_HIGHMEM64G=y
> CONFIG_SMP=n
> CONFIG_PCI=n
> CONFIG_IPV6=m
> $ make allyesconfig KCONFIG_ALLCONFIG=myconfig
> 

OK.  It would be nicer to be able to specify things via variables 
directly on the command line, but definitely fills the need.

	-hpa

      reply	other threads:[~2007-11-06  1:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-03 23:48 [PATCH] replace "make ARCH=i386/x86_64 with make ARCH=x86" Sam Ravnborg
2007-11-03 23:52 ` Arjan van de Ven
2007-11-04  1:17   ` Adrian Bunk
2007-11-04  2:02 ` Jeff Garzik
2007-11-04  2:48   ` Adrian Bunk
2007-11-04  6:20   ` Jeremy Fitzhardinge
2007-11-05 10:41 ` Christoph Hellwig
2007-11-05 17:17   ` Sam Ravnborg
2007-11-05 21:36     ` Roland Dreier
2007-11-05 21:49       ` Sam Ravnborg
2007-11-05 23:46         ` H. Peter Anvin
2007-11-06  0:40           ` Guillaume Chazarain
2007-11-06  0:47             ` H. Peter Anvin
2007-11-06  1:29           ` Adrian Bunk
2007-11-06  1:33             ` H. Peter Anvin [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=472FC454.4040701@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rdreier@cisco.com \
    --cc=sam@ravnborg.org \
    --cc=tglx@linutronix.de \
    /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 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.