From: Jeremy Fitzhardinge <jeremy@goop.org>
To: yamahata@valinux.co.jp
Cc: linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
xen-devel@lists.xensource.com, linux-ia64@vger.kernel.org,
xen-ia64-devel@lists.xensource.com,
Chris Wright <chrisw@sous-sol.org>,
"Stephen C. Tweedie" <sct@redhat.com>
Subject: Re: [PATCH 03/11] xen: add missing definitions for xen grant table which ia64/xen needs.
Date: Thu, 21 Feb 2008 11:40:03 -0800 [thread overview]
Message-ID: <47BDD393.5080307@goop.org> (raw)
In-Reply-To: <20080221091001.314830000@ls.local.valinux.co.jp>
yamahata@valinux.co.jp wrote:
Yep. We removed the guest handle stuff for the initial upstreaming,
since it isn't necessary on x86 and it quietened some of the reviewer
noise. But I expected we'd need to reintroduce it at some stage.
J
next prev parent reply other threads:[~2008-02-21 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080221084530.470680000@ls.local.valinux.co.jp>
2008-02-21 19:35 ` [PATCH 00/11] Xen arch portability patches Jeremy Fitzhardinge
[not found] ` <20080221091002.222498000@ls.local.valinux.co.jp>
2008-02-21 19:38 ` [PATCH 06/11] xen: move arch/x86/xen/events.c undedr drivers/xen and split out arch specific part Jeremy Fitzhardinge
2008-02-22 3:47 ` Isaku Yamahata
[not found] ` <20080221091001.314830000@ls.local.valinux.co.jp>
2008-02-21 19:40 ` Jeremy Fitzhardinge [this message]
2008-02-22 5:07 [PATCH 00/11] Xen arch portability patches Isaku Yamahata
2008-02-22 5:07 ` [PATCH 03/11] xen: add missing definitions for xen grant table which ia64/xen needs Isaku Yamahata
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=47BDD393.5080307@goop.org \
--to=jeremy@goop.org \
--cc=chrisw@sous-sol.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-devel@lists.xensource.com \
--cc=yamahata@valinux.co.jp \
/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