From: john stultz <johnstul@us.ibm.com>
To: Patrick Mochel <mochel@osdl.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>, Dave Jones <davej@suse.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Greg KH <greg@kroah.com>,
george anzinger <george@mvista.com>
Subject: Re: [PATCH] linux-2.5.40_timer-changes_A3 (1/3 - infrastructure)
Date: 03 Oct 2002 10:48:22 -0700 [thread overview]
Message-ID: <1033667302.28783.152.camel@cog> (raw)
In-Reply-To: <Pine.LNX.4.44.0210030922210.27710-100000@cherise.pdx.osdl.net>
On Thu, 2002-10-03 at 09:28, Patrick Mochel wrote:
>
> > Inspired by suggestions from Alan, this collection of patches tries to
> > clean up time.c by breaking out the PIT and TSC specific parts into
> > their own files. Additionally the patch creates an abstract interface to
> > use these existing time soruces, as well as make it easier to add future
> > time sources.
>
> I would suggest taking it one small step farther and putting everything in
> their own subdirectory. Like arch/i386/kernel/timer/, at least for now. IF
> we ever get an arch/i386/driver/ subdir, it's simple enough to move the
> dir. One way or another, it unclutters the directory while achieving the
> same cleanup.
That sounds good. I'll do so before I resubmit.
Thanks for the feedback!
-john
prev parent reply other threads:[~2002-10-03 17:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 6:09 [PATCH] linux-2.5.40_timer-changes_A3 (1/3 - infrastructure) john stultz
2002-10-03 6:11 ` [PATCH] linux-2.5.40_timer-changes_A3 (2/3 - bulk move) john stultz
2002-10-03 6:12 ` [PATCH] linux-2.5.40_timer-changes_A3 (3/3 - integration) john stultz
2002-10-03 6:59 ` Greg KH
2002-10-03 7:13 ` john stultz
2002-10-03 7:28 ` Greg KH
2002-10-03 7:33 ` john stultz
2002-10-03 6:13 ` [RFC][PATCH] linux-2.5.40_cyclone-timer_B2 john stultz
2002-10-03 16:28 ` [PATCH] linux-2.5.40_timer-changes_A3 (1/3 - infrastructure) Patrick Mochel
2002-10-03 17:48 ` john stultz [this message]
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=1033667302.28783.152.camel@cog \
--to=johnstul@us.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@suse.de \
--cc=george@mvista.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=torvalds@transmeta.com \
/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.