public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: xen-devel@lists.xenproject.org
Cc: Paul Bolle <pebolle@tiscali.nl>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Tony Luck <tony.luck@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] ia64/xen: Remove Xen support for ia64 even more
Date: Mon, 10 Feb 2014 09:56:13 -0500	[thread overview]
Message-ID: <52F8E88D.3020600@oracle.com> (raw)
In-Reply-To: <1391898943.27190.5.camel@x220>

On 02/08/2014 05:35 PM, 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.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> ---
> Basically only tested with "git grep". There's a chance I might have
> missed some second order effects.
>
>   drivers/xen/Makefile            |   1 -
>   drivers/xen/xencomm.c           | 219 ----------------------------------------
>   include/xen/interface/xencomm.h |  41 --------
>   include/xen/xencomm.h           |  77 --------------
>   4 files changed, 338 deletions(-)
>   delete mode 100644 drivers/xen/xencomm.c
>   delete mode 100644 include/xen/interface/xencomm.h
>   delete mode 100644 include/xen/xencomm.h

Speaking of xencomm, do we still need it in Xen tree?

-boris


      parent reply	other threads:[~2014-02-10 14:55 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
2014-02-10 14:56 ` Boris Ostrovsky [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=52F8E88D.3020600@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@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