From: Jeremy Fitzhardinge <jeremy@goop.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 09/32] ia64/xen: add a necessary header file to compile
Date: Tue, 14 Oct 2008 22:42:46 +0000 [thread overview]
Message-ID: <48F52066.5040604@goop.org> (raw)
In-Reply-To: <1223963507-28056-10-git-send-email-yamahata@valinux.co.jp>
Luck, Tony wrote:
> +++ b/arch/ia64/include/asm/pvclock-abi.h
> @@ -0,0 +1,5 @@
> +/*
> + * use same structure to x86's
> + * Hopefully asm-x86/pvclock-abi.h would be moved to somewhere more generic.
> + */
> +#include <asm-x86/pvclock-abi.h>
>
>
> I will trade out this patch for one that just makes
> a copy of the x86 include file. This #include will
> break if/when x86 moves their include files to
> arch/x86/include/asm
>
I think Ingo is planning it fairly soon.
J
next prev parent reply other threads:[~2008-10-14 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 5:51 [PATCH 09/32] ia64/xen: add a necessary header file to compile include/xen/interface/xen.h Isaku Yamahata
2008-10-14 21:46 ` [PATCH 09/32] ia64/xen: add a necessary header file to compile Luck, Tony
2008-10-14 22:42 ` Jeremy Fitzhardinge [this message]
2008-10-15 3:18 ` [PATCH 09/32] ia64/xen: add a necessary header file to compile include/xen/interface/xen.h 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=48F52066.5040604@goop.org \
--to=jeremy@goop.org \
--cc=linux-ia64@vger.kernel.org \
/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