From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
xen-ia64-devel@lists.xensource.com, eddie.dong@intel.com
Subject: Re: [PATCH 0/3] xen: more portability patches
Date: Sat, 26 Apr 2008 01:42:16 -0700 [thread overview]
Message-ID: <4812EAE8.5000006@goop.org> (raw)
In-Reply-To: <12088476062604-git-send-email-yamahata@valinux.co.jp>
Isaku Yamahata wrote:
> Hi Jeremy.
> Here are the 3 patches for ia64/xen support.
> The first one is just to move manage.c under drivers/xen.
> This is trivial.
>
> The second and third ones are for compilation fix on ia64.
> You may want to postpone those 2 patches to make your merge task
> easy as you said before.
>
I've put these into my queue. I'll submit them to Ingo when the merge
window settles down.
J
next prev parent reply other threads:[~2008-04-26 8:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 7:00 [PATCH 0/3] xen: more portability patches Isaku Yamahata
2008-04-22 7:00 ` [PATCH 1/3] xen: Move manage.c to drivers/xen for ia64/xen support Isaku Yamahata
2008-04-22 7:00 ` Isaku Yamahata
2008-04-24 0:00 ` Jeremy Fitzhardinge
2008-04-24 0:00 ` Jeremy Fitzhardinge
2008-04-22 7:00 ` [PATCH 2/3] xen: add missing definitions in include/xen/interface/memory.h which ia64/xen needs Isaku Yamahata
2008-04-22 7:00 ` Isaku Yamahata
2008-04-22 7:00 ` [PATCH 3/3] xen: compilation fix to balloon driver for ia64 support Isaku Yamahata
2008-04-22 7:00 ` Isaku Yamahata
2008-04-26 8:42 ` [PATCH 0/3] xen: more portability patches Jeremy Fitzhardinge
2008-04-26 8:42 ` Jeremy Fitzhardinge [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-22 7:00 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=4812EAE8.5000006@goop.org \
--to=jeremy@goop.org \
--cc=eddie.dong@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.