From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Walker <dwalker@mvista.com>
Cc: David Brownell <david-b@pacbell.net>,
linux-kernel@vger.kernel.org, john stultz <johnstul@us.ibm.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 14/23] clocksource: increase initcall priority
Date: Thu, 01 Feb 2007 01:34:43 +0100 [thread overview]
Message-ID: <1170290084.29240.246.camel@localhost.localdomain> (raw)
In-Reply-To: <1170288912.9781.177.camel@imap.mvista.com>
On Wed, 2007-01-31 at 16:15 -0800, Daniel Walker wrote:
> > clocksource_initcall is simply superfluid.
>
> My position has always been that clocksources should be registered as
> early as possible .. The fs_initcall() usage is a compromise stemming
> from early resistance that John, and you gave to moving the clocks up in
> the initcall sequence.
No. I never objected against the registering of clocks at any given
time. Why would I have otherwise accepted ARM patches, which register
their clocksources in the early timer init ?
The only concern I had and still have is when we decide to use something
else than the "safe" heaven of jiffies.
tglx
next prev parent reply other threads:[~2007-02-01 0:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 19:43 David Brownell
2007-01-31 22:47 ` Daniel Walker
2007-01-31 23:23 ` Thomas Gleixner
2007-02-01 0:15 ` Daniel Walker
2007-02-01 0:34 ` Thomas Gleixner [this message]
2007-02-01 0:24 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2007-01-31 3:37 [PATCH 00/23] clocksource update v12 Daniel Walker
2007-01-31 3:37 ` [PATCH 14/23] clocksource: increase initcall priority Daniel Walker
2007-01-31 11:50 ` Ingo Molnar
2007-01-31 16:42 ` Daniel Walker
2007-01-31 17:10 ` Ingo Molnar
2007-01-31 17:20 ` Daniel Walker
2007-01-31 17:29 ` Thomas Gleixner
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=1170290084.29240.246.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=david-b@pacbell.net \
--cc=dwalker@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®