linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Michal Marek <mmarek@suse.cz>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] config: Add 'make kvmconfig'
Date: Fri, 28 Oct 2011 09:52:31 +0200	[thread overview]
Message-ID: <20111028075231.GA8626@elte.hu> (raw)
In-Reply-To: <1319788039.3235.13.camel@lappy>


* Sasha Levin <levinsasha928@gmail.com> wrote:

> On Fri, 2011-10-28 at 09:39 +0200, Ingo Molnar wrote:
> > * Sasha Levin <levinsasha928@gmail.com> wrote:
> > 
> > > > ? It would be very obvious at a glance what it does.
> > > 
> > > We can possibly make 'make defconfig abc' run arch specific script 
> > > located next to the defconfig files (arch/$(ARCH)/configs/).
> > 
> > AFAICS that's not the same as the current kvmconfig functionality 
> > though: we want to minimally enable certain config options in the 
> > current .config - not pick some default config.
> 
> Yup, I wasn't planning on it to work like defconfig does where it 
> just uses a default config, thats why I said 'run arch specific 
> script' :)
> 
> That script could either copy over a default config, or simply add 
> config options like what we're interested in doing.

i'd be fine with that extension to defconfig functionality. It in 
fact makes much more sense than the *current* defconfig functionality 
which is kind of a joke (as it's really just an arbitrary config).

Thanks,

	Ingo

  reply	other threads:[~2011-10-28  7:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 12:07 [PATCH] config: Add 'make kvmconfig' Sasha Levin
2011-10-27 12:12 ` Pekka Enberg
2011-10-27 12:37   ` Ingo Molnar
2011-10-27 12:51     ` Michal Marek
2011-10-27 13:34       ` Ingo Molnar
2011-10-27 14:11       ` Pekka Enberg
2011-10-27 14:32         ` Michal Marek
2011-10-27 15:05           ` Arnaud Lacombe
2011-10-27 15:19         ` Arnaud Lacombe
2011-10-27 15:30           ` Pekka Enberg
2011-10-27 18:05 ` Rabin Vincent
2011-10-27 20:46   ` Sasha Levin
2011-10-27 19:34 ` Sam Ravnborg
2011-10-28  7:03   ` Ingo Molnar
2011-10-28  7:23     ` Sasha Levin
2011-10-28  7:39       ` Ingo Molnar
2011-10-28  7:47         ` Sasha Levin
2011-10-28  7:52           ` Ingo Molnar [this message]
2011-10-28  7:52     ` Geert Uytterhoeven
2011-10-28  7:54       ` Ingo Molnar
2011-10-28 12:08         ` Matthias Schniedermeyer
2011-10-28 12:29           ` Ingo Molnar
2011-10-28 13:05             ` Matthias Schniedermeyer
2011-11-02  8:41               ` Ingo Molnar
2011-11-02  9:07                 ` Michal Marek
2011-11-02  9:17                   ` Ingo Molnar
2011-11-02  9:24                     ` Michal Marek
2011-11-02  9:39                       ` Ingo Molnar
2011-11-02 10:06                         ` Pekka Enberg
2011-10-28  9:16       ` Sasha Levin

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=20111028075231.GA8626@elte.hu \
    --to=mingo@elte.hu \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=penberg@cs.helsinki.fi \
    --cc=sam@ravnborg.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).