From: Chris Wright <chrisw@osdl.org>
To: Zachary Amsden <zach@vmware.com>
Cc: akpm@osdl.org, chrisw@osdl.org, linux-kernel@vger.kernel.org,
davej@codemonkey.org.uk, hpa@zytor.com, Riley@Williams.Name,
pratap@vmware.com, chrisl@vmware.com
Subject: Re: [PATCH] 4/8 Move TLB flush definitions to the sub-architecture level
Date: Sat, 6 Aug 2005 18:09:08 -0700 [thread overview]
Message-ID: <20050807010908.GI7762@shell0.pdx.osdl.net> (raw)
In-Reply-To: <42F4639A.7090304@vmware.com>
* Zachary Amsden (zach@vmware.com) wrote:
> i386 Transparent Paravirtualization Patch #4
>
> This change encapsulates TLB flush accessors into the sub-architecture layer.
Hrm, same here (pushed too much to subarch), so I'll update that one
and report back tomorrow.
thanks,
-chris
prev parent reply other threads:[~2005-08-07 1:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-06 7:15 [PATCH] 4/8 Move TLB flush definitions to the sub-architecture level Zachary Amsden
2005-08-07 1:09 ` Chris Wright [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=20050807010908.GI7762@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=Riley@Williams.Name \
--cc=akpm@osdl.org \
--cc=chrisl@vmware.com \
--cc=davej@codemonkey.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pratap@vmware.com \
--cc=zach@vmware.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