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-devel@lists.xensource.com,
xen-ia64-devel@lists.xensource.com, linux-ia64@vger.kernel.org
Subject: Re: [PATCH] xen: compilation fix for ia64 support.
Date: Thu, 03 Jul 2008 21:51:03 +0000 [thread overview]
Message-ID: <486D49C7.5070702@goop.org> (raw)
In-Reply-To: <20080703070952.GB15683%yamahata@valinux.co.jp>
Isaku Yamahata wrote:
> don't include asm/pvclock-abi.h directly, but asm/xen/pvclock-abi.h
> At this moment linux ia64 won't accept asm/pvclock-abi.h because
> there's no user of it.
Huh? Is this a ia64 maintainer policy? Aren't you about to start using it?
> Instead make it include asm/xen/pvclock-abi.h
> and create asm-x86/xen/pvclock-abi.h which includes asm-x86/pvclock-abi.h.
>
I'm not very keen on crufting up asm-x86/xen/ for the ia64 code.
Couldn't you have an asm-ia64/xen/pvclock-abi.h which includes
<asm-x86/pvclock-abi.h>?
J
WARNING: multiple messages have this Message-ID (diff)
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-devel@lists.xensource.com,
xen-ia64-devel@lists.xensource.com, linux-ia64@vger.kernel.org
Subject: Re: [PATCH] xen: compilation fix for ia64 support.
Date: Thu, 03 Jul 2008 14:51:03 -0700 [thread overview]
Message-ID: <486D49C7.5070702@goop.org> (raw)
In-Reply-To: <20080703070952.GB15683%yamahata@valinux.co.jp>
Isaku Yamahata wrote:
> don't include asm/pvclock-abi.h directly, but asm/xen/pvclock-abi.h
> At this moment linux ia64 won't accept asm/pvclock-abi.h because
> there's no user of it.
Huh? Is this a ia64 maintainer policy? Aren't you about to start using it?
> Instead make it include asm/xen/pvclock-abi.h
> and create asm-x86/xen/pvclock-abi.h which includes asm-x86/pvclock-abi.h.
>
I'm not very keen on crufting up asm-x86/xen/ for the ia64 code.
Couldn't you have an asm-ia64/xen/pvclock-abi.h which includes
<asm-x86/pvclock-abi.h>?
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: xen-ia64-devel@lists.xensource.com,
xen-devel@lists.xensource.com, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] xen: compilation fix for ia64 support.
Date: Thu, 03 Jul 2008 14:51:03 -0700 [thread overview]
Message-ID: <486D49C7.5070702@goop.org> (raw)
In-Reply-To: <20080703070952.GB15683%yamahata@valinux.co.jp>
Isaku Yamahata wrote:
> don't include asm/pvclock-abi.h directly, but asm/xen/pvclock-abi.h
> At this moment linux ia64 won't accept asm/pvclock-abi.h because
> there's no user of it.
Huh? Is this a ia64 maintainer policy? Aren't you about to start using it?
> Instead make it include asm/xen/pvclock-abi.h
> and create asm-x86/xen/pvclock-abi.h which includes asm-x86/pvclock-abi.h.
>
I'm not very keen on crufting up asm-x86/xen/ for the ia64 code.
Couldn't you have an asm-ia64/xen/pvclock-abi.h which includes
<asm-x86/pvclock-abi.h>?
J
next prev parent reply other threads:[~2008-07-03 21:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 7:09 [PATCH] xen: compilation fix for ia64 support Isaku Yamahata
2008-07-03 7:09 ` Isaku Yamahata
2008-07-03 7:09 ` Isaku Yamahata
2008-07-03 21:51 ` Jeremy Fitzhardinge
2008-07-03 21:51 ` Jeremy Fitzhardinge [this message]
2008-07-03 21:51 ` Jeremy Fitzhardinge
2008-07-03 21:51 ` Jeremy Fitzhardinge
2008-07-04 2:41 ` Isaku Yamahata
2008-07-04 2:41 ` Isaku Yamahata
2008-07-04 2:41 ` Isaku Yamahata
-- strict thread matches above, loose matches on Subject: below --
2008-07-03 7:09 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=486D49C7.5070702@goop.org \
--to=jeremy@goop.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.