From: john stultz <johnstul@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] linux-2.6.3_ia64-cyclone_A2.patch
Date: Wed, 18 Feb 2004 21:49:44 +0000 [thread overview]
Message-ID: <1077140984.985.118.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <1077136393.985.111.camel@cog.beaverton.ibm.com>
On Wed, 2004-02-18 at 13:36, David Mosberger wrote:
> >>>>> On Wed, 18 Feb 2004 12:33:14 -0800, john stultz <johnstul@us.ibm.com> said:
>
> john> This patch provides access to the cyclone time source found on IBM EXA
> john> based systems (x450 and x455). This is needed on multi-node systems
> john> where the CPU ITCs are not synchronized, causing possible time
> john> inconsistencies.
>
> john> This release fixes one last minor think-o and ran overnight without any
> john> time inconsistencies (when used in conjunction w/ the
> john> time-interpolator-fix_A0 patch).
>
> john> Please consider for inclusion into your tree.
>
> The current patch looks mostly fine to me (apart from the trailing
> whitespace again). I'm wondering though whether cyclone.c should go
> into arch/ia64/ibm/SOMEWHERE, like we do for the SGI and HP
> platform-specific code. Or, if Cyclone sharable with your x86-based
> platforms, perhaps it should even go somewhere in drivers?
Gah! Where is this trailing whitespace? I went through this patch
specifically eliminating any I could find. Perhaps my mail client is
trying to irritate me.
The code, while similar, isn't quite shareable w/ ia32. However, I'd be
up for moving it to a separate IBM directory if you'd prefer, although
for just a single file it seems like overkill.
thanks
-john
next prev parent reply other threads:[~2004-02-18 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 20:33 [PATCH] linux-2.6.3_ia64-cyclone_A2.patch john stultz
2004-02-18 21:36 ` David Mosberger
2004-02-18 21:41 ` David Mosberger
2004-02-18 21:49 ` john stultz [this message]
2004-02-18 21:52 ` john stultz
2004-02-18 22:03 ` David Mosberger
2004-02-18 22:24 ` john stultz
2004-02-18 22:35 ` David Mosberger
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=1077140984.985.118.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=linux-ia64@vger.kernel.org \
/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