[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071030214601.GA19598@uranus.ravnborg.org>
Date: Tue, 30 Oct 2007 22:46:01 +0100
From: Sam Ravnborg <sam@...nborg.org>
To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Jeff Garzik <jeff@...zik.org>,
Randy Dunlap <rdunlap@...otime.net>, hch@...radead.org,
linux-kernel@...r.kernel.org, Jens Axboe <jens.axboe@...cle.com>,
Prasanna S Panchamukhi <prasanna@...ibm.com>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
"David S. Miller" <davem@...emloft.net>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <pzijlstr@...hat.com>,
Philippe Elie <phil.el@...adoo.fr>,
"William L. Irwin" <wli@...omorphy.com>,
Arjan van de Ven <arjan@...radead.org>,
Christoph Lameter <christoph@...eter.com>,
Valdis.Kletnieks@...edu
Subject: Re: [RFC] Create kinst/ or ki/ directory ?
>
> Should it come with a re-duplication of it's content into each
> architecture, which was the case previously ? The oprofile and kprobes menu
> entries were litteraly cut and pasted from one architecture to another.
> Should we put its content in init/Kconfig then ?
Stuff it into a new file: arch/Kconfig
We can then extend this file to include all the 'trailing'
Kconfig things that are anyway equal for all ARCHs.
But it should be kept clean - so if we introduce such a file
then we should use ARCH_HAS_whatever in the arch specific Kconfig
files to enable stuff that is not shared.
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