From: David Vrabel <david.vrabel@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Paul Bolle <pebolle@tiscali.nl>, Tony Luck <tony.luck@intel.com>,
<linux-kernel@vger.kernel.org>, <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] [PATCH] ia64/xen: Remove Xen support for ia64 even more
Date: Mon, 10 Feb 2014 13:37:59 +0000 [thread overview]
Message-ID: <52F8D637.30204@citrix.com> (raw)
In-Reply-To: <52F8D2C5.6040507@citrix.com>
On 10/02/14 13:23, David Vrabel wrote:
> On 08/02/14 22:35, Paul Bolle wrote:
>> Commit d52eefb47d4e ("ia64/xen: Remove Xen support for ia64") removed
>> the Kconfig symbol XEN_XENCOMM. But it didn't remove the code depending
>> on that symbol. Remove that code now.
>
> Acked-by: David Vrabel <david.vrabel@citrix.com>
Forgot to say, since this only touches drivers/xen this is best merged
via the Xen tree.
Thanks
David
next prev parent reply other threads:[~2014-02-10 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 22:35 [PATCH] ia64/xen: Remove Xen support for ia64 even more Paul Bolle
2014-02-10 13:23 ` [Xen-devel] " David Vrabel
2014-02-10 13:37 ` David Vrabel [this message]
2014-02-10 14:56 ` Boris Ostrovsky
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=52F8D637.30204@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=tony.luck@intel.com \
--cc=xen-devel@lists.xenproject.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