xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Olaf Hering <olaf@aepfle.de>,
	Ian.Jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH 00/11] tools changes
Date: Wed, 12 Mar 2014 11:17:29 -0400	[thread overview]
Message-ID: <53207A89.8030506@oracle.com> (raw)
In-Reply-To: <1394636508.3457.2.camel@kazak.uk.xensource.com>

On 03/12/2014 11:01 AM, Ian Campbell wrote:
> On Wed, 2014-03-12 at 10:41 -0400, Boris Ostrovsky wrote:
>> On 03/06/2014 11:13 AM, Olaf Hering wrote:
>>> Resend of changes from the 4.4 freeze time.
>>>
>>> Olaf Hering (11):
>>>     docs: remove ia64 from kexec_and_kdump.txt
>>>     unmodified_drivers: remove ia64 parts of the code
>>>     docs: remove ia64 from tmem-internals.html
>>>     stubdom: remove ia64 from stubdom
>>>     libxc: remove ia64 from xg_private.h
>>>     pygrub: remote ia64 from pygrub
>>>     xend: remove ia64 from xend sources
>>>     libxl: add option for discard support to xl disk configuration
>>>     tools/xc: pass errno to callers of xc_domain_save
>>>     xend/pvscsi: recognize also SCSI CDROM devices
>>>     tools/xend: move assert to exception block
>>
>> This reminds me: do we still need xencomm? My understanding is that it
>> was only used by ia64 (and ppc?) and Linux recently removed support for
>> it. I don't know whether other OSs use it.
> My understanding was that it was a ppc thing, not sure about ia64.
>
> Neither x86 nor arm uses it AFAIK. I'm not entirely sure what its
> purpose actually was.

Then it sounds like we should be able to remove it.

I can send a patch unless one of the maintainers wants to do it (i.e. 
remove relevant files and update Makefiles).

-boris

      reply	other threads:[~2014-03-12 15:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 16:13 [PATCH 00/11] tools changes Olaf Hering
2014-03-06 16:13 ` [PATCH 01/11] docs: remove ia64 from kexec_and_kdump.txt Olaf Hering
2014-03-06 16:13 ` [PATCH 02/11] unmodified_drivers: remove ia64 parts of the code Olaf Hering
2014-03-12 13:37   ` Ian Campbell
2014-03-12 14:14   ` Jan Beulich
2014-03-12 14:26     ` Olaf Hering
2014-03-12 15:04       ` Jan Beulich
2014-03-06 16:13 ` [PATCH 03/11] docs: remove ia64 from tmem-internals.html Olaf Hering
2014-03-06 16:13 ` [PATCH 04/11] stubdom: remove ia64 from stubdom Olaf Hering
2014-03-06 16:13 ` [PATCH 05/11] libxc: remove ia64 from xg_private.h Olaf Hering
2014-03-06 16:13 ` [PATCH 06/11] pygrub: remote ia64 from pygrub Olaf Hering
2014-03-06 18:04   ` Ian Jackson
2014-03-06 18:59     ` Olaf Hering
2014-03-07 11:06       ` Ian Jackson
2014-03-06 16:13 ` [PATCH 07/11] xend: remove ia64 from xend sources Olaf Hering
2014-03-06 16:13 ` [PATCH 08/11] libxl: add option for discard support to xl disk configuration Olaf Hering
2014-03-06 18:15   ` Ian Jackson
2014-03-06 19:11     ` Olaf Hering
2014-03-06 16:13 ` [PATCH 09/11] tools/xc: pass errno to callers of xc_domain_save Olaf Hering
2014-03-06 18:17   ` Ian Jackson
2014-03-06 19:19     ` Olaf Hering
2014-03-10 16:49       ` Ian Jackson
2014-03-11  8:21         ` Olaf Hering
2014-03-11 11:18           ` Ian Jackson
2014-03-06 16:13 ` [PATCH 10/11] xend/pvscsi: recognize also SCSI CDROM devices Olaf Hering
2014-03-06 18:19   ` Ian Jackson
2014-03-06 19:20     ` Olaf Hering
2014-03-06 16:13 ` [PATCH 11/11] tools/xend: move assert to exception block Olaf Hering
2014-03-06 18:07 ` [PATCH 00/11] tools changes Ian Jackson
2014-03-12 14:41 ` Ian Campbell
2014-03-12 14:41 ` Boris Ostrovsky
2014-03-12 15:01   ` Ian Campbell
2014-03-12 15:17     ` 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=53207A89.8030506@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).