From: Alex Williamson <alex.williamson@hp.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, tony.luck@intel.com
Subject: Re: [PATCH] optimize writer path in time_interpolator_get_counter()
Date: Mon, 01 Aug 2005 10:10:57 -0600 [thread overview]
Message-ID: <1122912657.5243.25.camel@tdi> (raw)
In-Reply-To: <Pine.LNX.4.62.0508010906250.6397@schroedinger.engr.sgi.com>
On Mon, 2005-08-01 at 09:06 -0700, Christoph Lameter wrote:
> Could we remove some code duplication?
Works for me. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
next prev parent reply other threads:[~2005-08-01 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-01 15:52 [PATCH] optimize writer path in time_interpolator_get_counter() Alex Williamson
2005-08-01 16:06 ` Christoph Lameter
2005-08-01 16:10 ` Alex Williamson [this message]
2005-08-02 18:37 ` tony.luck
2005-08-02 21:19 ` Christoph Lameter
2005-08-03 14:42 ` Alex Williamson
2005-08-03 16:10 ` Christoph Lameter
2005-08-03 16:32 ` Alex Williamson
2005-08-03 20:49 ` Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2005-08-02 21:50 Luck, Tony
2005-08-02 22:09 ` Christoph Lameter
2005-08-03 17:00 Luck, Tony
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=1122912657.5243.25.camel@tdi \
--to=alex.williamson@hp.com \
--cc=akpm@osdl.org \
--cc=clameter@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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