[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080201133931.GB13349@uranus.ravnborg.org>
Date: Fri, 1 Feb 2008 14:39:31 +0100
From: Sam Ravnborg <sam@...nborg.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: Heiko Carstens <heiko.carstens@...ibm.com>,
Arjan van de Ven <arjan@...ux.intel.com>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
Holger Wolf <wolf@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] latencytop: Change Kconfig dependency.
On Fri, Feb 01, 2008 at 02:32:28PM +0100, Ingo Molnar wrote:
>
> * Sam Ravnborg <sam@...nborg.org> wrote:
>
> > > config STACKTRACE_SUPPORT
> > > def_bool y
> > >
> > > +config HAVE_LATENCYTOP_SUPPORT
> > > + def_bool y
> > > +
> > No.
> > Please do:
> > config X86
> > + select HAVE_LATENCYTOP_SUPPORT
> >
> > Yes - this is a valid use of select.
>
> i see - and there's lots of other examples of this and other similar
> things in other architectures as well. Could we do that as a separate
> cleanup patch instead, to keep the Kconfig file consistently structured.
I would prefer new stuff to use the recommended method.
But I have no strong feelign for it and at the moment I am fed up
in Section mismatch warnings :-(
Sam
--
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