From: john stultz <johnstul@us.ibm.com>
To: dsaxena@plexity.net
Cc: mingo@elte.hu, tglx@linutronix.de, dwalker@mvista.com,
james.perkins@windriver.com, linux-kernel@vger.kernel.org,
rmk@arm.linux.org.uk, khilman@mvista.com
Subject: Re: [patch-rt 1/2] Remove existing time code from ARM architecture
Date: Mon, 05 Jun 2006 16:13:32 -0700 [thread overview]
Message-ID: <1149549212.11470.20.camel@localhost.localdomain> (raw)
In-Reply-To: <20060605224438.054796000@localhost.localdomain>
On Mon, 2006-06-05 at 15:29 -0700, dsaxena@plexity.net wrote:
> plain text document attachment (arm-generic-timeofday.patch)
> This patch removes do_gettimeofday(), do_setttimeofday() and associated
> time functions from ARM so that it can use the generic time-of-day code.
> Each sub-arch must explicitly enable CONFIG_IS_TICK_BASED if it does
> not have continous timer source.
It might be good to define CONFIG_IS_TICK_BASED for the other ARM arches
so they continue to build after your changes. Otherwise it looks good to
me.
Another aside: CONFIG_IS_TICK_BASED also goes away w/ the Cx series. So
there you will want to conditionally enable GENERIC_TIME if you have a
clocksources defined and just wrap the old get/set_timeofday() w/ ifndef
CONFIG_GENERIC_TIME until all the sub-arches have been converted. Don't
worry too much, I'll lend a hand here when the time comes to update -rt,
so it shouldn't be much of an issue.
thanks
-john
next prev parent reply other threads:[~2006-06-05 23:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 22:29 [patch-rt 0/2] Initial ARM generic-timeofday support dsaxena
2006-06-05 22:29 ` [patch-rt 1/2] Remove existing time code from ARM architecture dsaxena
2006-06-05 23:13 ` john stultz [this message]
2006-06-05 22:29 ` [patch-rt 2/2] Add clocksource driver for Versatile board dsaxena
2006-06-05 23:17 ` john stultz
2006-06-05 23:06 ` [patch-rt 0/2] Initial ARM generic-timeofday support john stultz
2006-06-05 23:13 ` Deepak Saxena
2006-06-05 23:16 ` john stultz
2006-06-06 20:05 ` Kevin Hilman
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=1149549212.11470.20.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=dsaxena@plexity.net \
--cc=dwalker@mvista.com \
--cc=james.perkins@windriver.com \
--cc=khilman@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rmk@arm.linux.org.uk \
--cc=tglx@linutronix.de \
/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.