From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] linux-2.6.3_ia64-cyclone_A2.patch
Date: Wed, 18 Feb 2004 22:03:22 +0000 [thread overview]
Message-ID: <16435.57642.819103.775542@napali.hpl.hp.com> (raw)
In-Reply-To: <1077136393.985.111.camel@cog.beaverton.ibm.com>
>>>>> On Wed, 18 Feb 2004 13:52:03 -0800, john stultz <johnstul@us.ibm.com> said:
John> Unfortunately there is no replicated clock on this hardware,
John> so all nodes access the first counter on the first node. Not
John> great, but correct and slow is better then fast and wrong.
OK, thanks for the info. I'll try to keep this in mind should there
be timestamping questions again (as there was recently in the
scheduler).
>>>>> On Wed, 18 Feb 2004 13:49:44 -0800, john stultz <johnstul@us.ibm.com> said:
John> Gah! Where is this trailing whitespace?
I already deleted the whitespace (my editor is showing it in bright
red, so it's kind a hard to ignore ;-).
John> I went through this patch specifically eliminating any I could
John> find. Perhaps my mail client is trying to irritate me.
The whitespace wasn't systematic, so i doubt it was the mailer.
Any chance the mail contained an old patch?
John> The code, while similar, isn't quite shareable w/
John> ia32. However, I'd be up for moving it to a separate IBM
John> directory if you'd prefer, although for just a single file it
John> seems like overkill.
I don't feel very strongly about it. If you expect there to be other
IBM-platform specific files in the future, it would make sense to
create an ibm subdirectory. It's really your call.
--david
next prev parent reply other threads:[~2004-02-18 22:03 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
2004-02-18 21:52 ` john stultz
2004-02-18 22:03 ` David Mosberger [this message]
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=16435.57642.819103.775542@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.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