From: "Guillaume Chazarain" <guichaz@yahoo.fr>
To: "H. Peter Anvin" <hpa@zytor.com>
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: Tue, 6 Nov 2007 01:40:14 +0100 [thread overview]
Message-ID: <3d8471ca0711051640w33588d8fn2c0e4aecf99d3547@mail.gmail.com> (raw)
In-Reply-To: <472FAB4C.9040303@zytor.com>
On 11/6/07, H. Peter Anvin <hpa@zytor.com> 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.
I don't know enough about Kbuild to know if it's possible or not, but I
would find it great if the *config targets could take CONFIG_ variables
on the command line, like:
make oldconfig CONFIG_SMP=y
If it's not possible, why not inherit the CONFIG_ options from environment
variables, like we already do for $CFLAGS, but only at make *config
time in this case?
--
Guillaume
next prev parent reply other threads:[~2007-11-06 0:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 23:48 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 [this message]
2007-11-06 0:47 ` H. Peter Anvin
2007-11-06 1:29 ` Adrian Bunk
2007-11-06 1:33 ` H. Peter Anvin
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=3d8471ca0711051640w33588d8fn2c0e4aecf99d3547@mail.gmail.com \
--to=guichaz@yahoo.fr \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®