From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>, Olaf Hering <olaf@aepfle.de>
Cc: ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] xl: suppress suspend/resume functions on platforms which do not support it.
Date: Wed, 12 Feb 2014 16:49:39 +0000 [thread overview]
Message-ID: <52FBA623.2010809@eu.citrix.com> (raw)
In-Reply-To: <1392220651.13563.86.camel@kazak.uk.xensource.com>
On 02/12/2014 03:57 PM, Ian Campbell wrote:
> On Wed, 2014-02-12 at 16:21 +0100, Olaf Hering wrote:
>> On Wed, Feb 12, Ian Campbell wrote:
>>
>>> #define LIBXL_HAVE_SIGCHLD_SHARING 1
>>>
>>> +/*
>>> + * LIBXL_HAVE_NO_SUSPEND_RESUME
>> Think positive?
>> Make that HAVE_FEATURE and define it on x86.
> Could do -- anyone got any strong feeling one way or the other?
I'm a fan of consistency, so "HAVE_SUSPEND" sounds a little bit better
to me. But either way is fine.
-George
next prev parent reply other threads:[~2014-02-12 16:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 14:27 [PATCH] xl: suppress suspend/resume functions on platforms which do not support it Ian Campbell
2014-02-12 14:32 ` Ian Campbell
2014-02-12 14:54 ` Ian Jackson
2014-02-13 9:19 ` Ian Campbell
2014-02-14 5:42 ` Lai Jiangshan
2014-02-18 9:57 ` Ian Campbell
2014-02-12 16:48 ` George Dunlap
2014-02-12 14:32 ` [PATCH OSSTEST] Do not attempt migration tests if the platform doesn't " Ian Campbell
2014-02-12 14:58 ` Ian Jackson
2014-02-12 15:21 ` [PATCH] xl: suppress suspend/resume functions on platforms which do not " Olaf Hering
2014-02-12 15:57 ` Ian Campbell
2014-02-12 16:49 ` George Dunlap [this message]
2014-02-12 16:54 ` Ian Campbell
2014-02-12 17:00 ` Ian Campbell
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=52FBA623.2010809@eu.citrix.com \
--to=george.dunlap@eu.citrix.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 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.