[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111028122902.GA25323@elte.hu>
Date: Fri, 28 Oct 2011 14:29:03 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Matthias Schniedermeyer <ms@...d.de>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>,
Sam Ravnborg <sam@...nborg.org>,
Sasha Levin <levinsasha928@...il.com>,
linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Michal Marek <mmarek@...e.cz>,
Pekka Enberg <penberg@...helsinki.fi>,
linux-kbuild@...r.kernel.org
Subject: Re: [PATCH] config: Add 'make kvmconfig'
* Matthias Schniedermeyer <ms@...d.de> wrote:
> On 28.10.2011 09:54, Ingo Molnar wrote:
> >
> > * Geert Uytterhoeven <geert@...ux-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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists