From: Grant Grundler <iod00d@hp.com>
To: Jesse Barnes <jbarnes@sgi.com>
Cc: Jesse Barnes <jbarnes@engr.sgi.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org, tony.luck@intel.com,
linux-ia64@vger.kernel.org
Subject: Re: [PATCH] I/O space write barrier
Date: Fri, 22 Oct 2004 15:26:58 +0000 [thread overview]
Message-ID: <20041022152658.GB21472@cup.hp.com> (raw)
In-Reply-To: <200410212205.51672.jbarnes@sgi.com>
On Thu, Oct 21, 2004 at 10:05:50PM -0500, Jesse Barnes wrote:
> Ok, that makes sense. I'd like to update the documentation with a separate
> patch though, if that's ok with you.
Sure, if that's easier for you.
grant
prev parent reply other threads:[~2004-10-22 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 23:13 [PATCH] I/O space write barrier Jesse Barnes
2004-10-22 1:01 ` Grant Grundler
2004-10-22 3:05 ` Jesse Barnes
2004-10-22 4:26 ` Greg Banks
2004-10-22 15:26 ` Grant Grundler [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=20041022152658.GB21472@cup.hp.com \
--to=iod00d@hp.com \
--cc=akpm@osdl.org \
--cc=jbarnes@engr.sgi.com \
--cc=jbarnes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--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