From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>, Juergen Gross <jgross@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xen.org, Wei Liu <wei.liu2@citrix.com>,
stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH] libxc: remove most of tools/libxc/xc_dom_compat_linux.c
Date: Thu, 22 Oct 2015 16:38:07 +0100 [thread overview]
Message-ID: <1445528287.2374.15.camel@citrix.com> (raw)
In-Reply-To: <22056.65314.301337.452773@mariner.uk.xensource.com>
On Thu, 2015-10-22 at 16:22 +0100, Ian Jackson wrote:
> Juergen Gross writes ("Re: [Xen-devel] [PATCH] libxc: remove most of
> tools/libxc/xc_dom_compat_linux.c"):
> > On 10/06/2015 03:17 PM, Ian Campbell wrote:
> > > xc_dom_linux_build is implemented in terms of the non-compat xc_dom_*
> > > functions, so it should be possible to do what you want with out
> > > using the
> > > compat wrapper.
> > >
> > > If there is some obscure reason this isn't the case then we should
> > > fix
> > > that, not carry around the compat options for ever as a workaround
> > > (fixes
> > > include but are not limited to promoting xc_dom_linux_build into a
> > > non
> > > -compat helper).
>
> I agree with this approach.
>
> > Any further comments?
> >
> > Andrew, are you okay with Ian's statement?
> >
> > Ian, does this mean you are Ack-ing the patch?
>
> Accordingly, in the absence of renewed objections, or alternative
> proposals, the original patch is:
>
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
There was a conflict with "libxc: unify xc_dom_p2m_{host/guest}", where
xc_dom_p2m_host became xc_dom_p2m. I tried to resolve in what I thought was
the obvious way, but then I got many instances of:
In file included from libxl.c:19:0:
libxl_internal.h:1612:43: error: 'struct xc_dom_image' declared inside parameter list [-Werror]
struct xc_dom_image *dom);
^
libxl_internal.h:1612:43: error: its scope is only this definition or declaration, which is probably not what you want [-Werror]
Not sure if the original patch was wrong, has bit-rotted, or I messed up
the conflict resolution. This happens on all arches.
Actually, looking back at it, the added "struct xc_dom_image" in
libxl_arch.h is surely wrong, the right answer would be to include xc_dom.h
somewhere appropriate it might be tolerable to just leave it in xenguest.h.
Juergen, please investigate the build failure, fix the above and resubmit.
Ian.
next prev parent reply other threads:[~2015-10-22 15:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 11:35 [PATCH] libxc: remove most of tools/libxc/xc_dom_compat_linux.c Juergen Gross
2015-10-06 12:52 ` Andrew Cooper
2015-10-06 12:58 ` Wei Liu
2015-10-06 13:06 ` Andrew Cooper
2015-10-06 13:17 ` Ian Campbell
2015-10-19 10:36 ` Juergen Gross
2015-10-22 15:22 ` Ian Jackson
2015-10-22 15:38 ` Ian Campbell [this message]
2015-10-23 7:15 ` Juergen Gross
2015-10-23 9:42 ` Ian Campbell
2015-10-23 9:53 ` Juergen Gross
2015-10-23 10:11 ` Ian Campbell
2015-10-22 15:51 ` Andrew Cooper
2015-10-22 15:21 ` Wei Liu
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=1445528287.2374.15.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jgross@suse.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--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.