Subject: Re: [PATCHSET 0/10] Time: Generic Timekeeping (v.C1)
From: Thomas Gleixner <tglx@linutronix.de>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: john stultz <johnstul@us.ibm.com>, akpm@osdl.org,
       linux-kernel@vger.kernel.org, george@wildturkeyranch.net,
       Steven Rostedt <rostedt@goodmis.org>,
       Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>,
       Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>
In-Reply-To: <Pine.LNX.4.64.0603231209380.17704@scrub.home>
References: <20060323030547.19338.95102.sendpatchset@cog.beaverton.ibm.com>
	 <Pine.LNX.4.64.0603231209380.17704@scrub.home>
Content-Type: text/plain
Date: Thu, 23 Mar 2006 14:20:58 +0000
Message-Id: <1143123658.28099.12.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1093
Lines: 26

On Thu, 2006-03-23 at 13:48 +0100, Roman Zippel wrote:
> One general comment: Currently clock relevant source is scattered in 
> kernel/time/, drivers/clocksource and arch/... IMO it would be better to 
> keep at least the first two parts a bit closer, although I'm not sure how 
> to organize it better. I don't know if we can be so bold to add a toplevel 
> time/ (similiar to sound/) or maybe we organize a bit like drivers/ide/. 
> Anyway, maybe someone has a good idea to keep everything a bit closer 
> together.

IMO it makes completely sense to move the time/timer/clocks related
generic code into kernel/time.

drivers/clocksource holds drivers which can be shared between
architectures.

The other drivers really should stay in the architecture specific files
as they are often deeply embedded in the SoC or chipset support code.

	tglx


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/