From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Jackson Subject: Re: [PATCH v5 19/24] libxl: define LIBXL_HAVE_VNUMA Date: Fri, 13 Feb 2015 15:27:38 +0000 Message-ID: <21726.6122.66642.532447@mariner.uk.xensource.com> References: <1423770294-9779-1-git-send-email-wei.liu2@citrix.com> <1423770294-9779-20-git-send-email-wei.liu2@citrix.com> <21726.1642.499389.940904@mariner.uk.xensource.com> <20150213152149.GH13644@zion.uk.xensource.com> <21726.6073.865574.897031@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <21726.6073.865574.897031@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu , xen-devel@lists.xen.org, ian.campbell@citrix.com, dario.faggioli@citrix.com, ufimtseva@gmail.com, JBeulich@suse.com, andrew.cooper3@citrix.com List-Id: xen-devel@lists.xenproject.org Ian Jackson writes ("Re: [PATCH v5 19/24] libxl: define LIBXL_HAVE_VNUMA"): > Yes, something like that. It would be better if the precise wording > were more similar to that for the other HAVE macros. How about: > > * If this is defined the type libxl_vnode_info exists, and a > * field 'vnuma_nodes' is present in libxl_domain_build_info. > > or similar ? BTW, this may seem picky, but it is much easier to quickly find the relevant one out of a lot of textual descriptions if there aren't any unnecessary differences. Ian.