From: Christoph Lameter <christoph@lameter.com>
To: linux-ia64@vger.kernel.org
Subject: Re: final [hopefully] timer patches
Date: Sat, 17 Jul 2004 16:50:28 +0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0407170947210.1456@server.home> (raw)
In-Reply-To: <Pine.LNX.4.58.0407161057440.29976@schroedinger.engr.sgi.com>
On Fri, 16 Jul 2004, David Mosberger wrote:
> The fsys.S portion of the patch still doesn't apply. I think that's
> because your missing Ken's fix for fsys_gettimeofday() that went in
> recently.
The patch is against 2.6.8-rc1 which does not contain Ken's patch. I can
make a patch against your tree if you think its ready to get in.
> Also, it would be good if the common code for fsys_gettimeofday() and
> fsys_clock_get() could be factored (into a macro, probably, since you
> can't use the standard calling convention without switching to kernel
> stacks first).
Doing so is quite an unusual approach. I thought it was better to leave
things the way it is. I tried doing a subroutine but that resulted in a
lot of complications with saving state.
prev parent reply other threads:[~2004-07-17 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 18:24 final [hopefully] timer patches Christoph Lameter
2004-07-17 6:53 ` David Mosberger
2004-07-17 16:50 ` Christoph Lameter [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=Pine.LNX.4.58.0407170947210.1456@server.home \
--to=christoph@lameter.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