From: Ingo Molnar <mingo@elte.hu>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Sam Ravnborg <sam@ravnborg.org>,
Sasha Levin <levinsasha928@gmail.com>,
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 14:29:03 +0200 [thread overview]
Message-ID: <20111028122902.GA25323@elte.hu> (raw)
In-Reply-To: <20111028120856.GA29174@citd.de>
* Matthias Schniedermeyer <ms@citd.de> wrote:
> On 28.10.2011 09:54, Ingo Molnar wrote:
> >
> > * Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> >
> > > > ? It would be very obvious at a glance what it does.
> > >
> > > This fits in the generic "I have a .config and I want to enable an
> > > additional option" functionality:
> > >
> > > make oldconfig CONFIG_KVMTOOL_TEST_ENABLE=y
> > >
> > > Don't we already have that support? I seem to remember it flying
> > > by. Or was it just a proposal that never got implemented?
> >
> > Well, it would be nice to have something (much) shorter and more
> > obvious, as we really expect to use this frequently.
> >
> > Maybe:
> >
> > make oldconfig kvm
>
> Maybe something more obvious?:
> make modconfig kvm
> or
> make modconfig=kvm
Well, i run distinctly non-modular kernels so modconfig would not be
particularly good. Also, many of the features enabled are non-modular
core kernel features to begin with.
But i don't particularly care about how it's named, as long as
there's a sane and obvious shortcut for it.
Thanks,
Ingo
next prev parent reply other threads:[~2011-10-28 12:33 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
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 [this message]
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=20111028122902.GA25323@elte.hu \
--to=mingo@elte.hu \
--cc=geert@linux-m68k.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=ms@citd.de \
--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 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.