From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [Xen-devel] [PATCH 0/9] x86/apic: hooks for Xen dom0 support
Date: Fri, 13 Feb 2009 17:09:28 -0800 [thread overview]
Message-ID: <499619C8.8080106@goop.org> (raw)
In-Reply-To: <cover.1234573319.git.jeremy.fitzhardinge@citrix.com>
Jeremy Fitzhardinge wrote:
> From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
>
Er, sorry about that...
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH 0/9] x86/apic: hooks for Xen dom0 support
Date: Fri, 13 Feb 2009 17:09:28 -0800 [thread overview]
Message-ID: <499619C8.8080106@goop.org> (raw)
In-Reply-To: <cover.1234573319.git.jeremy.fitzhardinge@citrix.com>
Jeremy Fitzhardinge wrote:
> From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
>
Er, sorry about that...
J
next prev parent reply other threads:[~2009-02-14 1:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 1:07 [PATCH 0/9] x86/apic: hooks for Xen dom0 support Jeremy Fitzhardinge
2009-02-14 1:07 ` Jeremy Fitzhardinge
2009-02-14 1:09 ` Jeremy Fitzhardinge [this message]
2009-02-14 1:09 ` Jeremy Fitzhardinge
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=499619C8.8080106@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@citrix.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
--cc=yinghai@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 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.