From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-ia64@vger.kernel.org, xen-devel@lists.xensource.com,
xen-ia64-devel@lists.xensource.com, "Luck,
Tony" <tony.luck@intel.com>
Subject: Re: [PATCH] xen: portability clean up and some minor clean up for xencomm.c
Date: Thu, 03 Jul 2008 14:53:28 -0700 [thread overview]
Message-ID: <486D4A58.60003@goop.org> (raw)
In-Reply-To: <20080703071209.GD15683%yamahata@valinux.co.jp>
Isaku Yamahata wrote:
> clean up of xencomm.c. is_phys_contiguous() is arch dependent
> function that depends on how virtual memory are laid out.
> So split out the function into arch specific code.
>
I suppose. But given that ia64 is the only user of xencomm, I'm not too
concerned about it. And unless Arm uses it, I suspect it may always be
the only user...
J
prev parent reply other threads:[~2008-07-03 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 7:12 [PATCH] xen: portability clean up and some minor clean up for xencomm.c Isaku Yamahata
2008-07-03 21:53 ` Jeremy Fitzhardinge [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=486D4A58.60003@goop.org \
--to=jeremy@goop.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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