From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, Juergen Gross <jgross@suse.com>
Cc: stefano.stabellini@eu.citrix.com, ian.jackson@eu.citrix.com,
xen-devel@lists.xen.org
Subject: Re: [PATCH 00/13] tools: do cleanups related to libxc python bindings
Date: Mon, 16 Nov 2015 12:09:21 +0000 [thread overview]
Message-ID: <1447675761.27871.48.camel@citrix.com> (raw)
In-Reply-To: <20151112130130.GI24281@zion.uk.xensource.com>
On Thu, 2015-11-12 at 13:01 +0000, Wei Liu wrote:
> On Mon, Nov 09, 2015 at 04:19:24PM +0100, Juergen Gross wrote:
> > On 10/23/2015 03:04 PM, Juergen Gross wrote:
> > > This series is a combination of my previous patches:
> > >
> > > "libxc: remove most of tools/libxc/xc_dom_compat_linux.c"
> > > "tools: remove unused wrappers for python"
> > >
> > > I have split it up as requested by Ian Campbell, thus it consists of
> > > 13 patches instead just of 2, but the functionality is roughly the
> > > same. I have just kept more python bindings compared to the first
> > > version, as there have been reports of some out of tree uses. Asking
> > > for more such use case on xen-devel and xen-user didn't result in
> > > requests for more interfaces to be kept, so I delete them.
> >
> > There have been acks and critical responses regarding this series.
Have there? I don't have the stashed alongside the series as I would
normally, so maybe I've missed them?
> > What should we do?
> >
> > - drop them all
> > - apply the first two patches only to get rid of the extra interfaces
> > to the domain builder as requested by Ian Campbell
>
> I would go for this.
I've done this one.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-11-16 12:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 13:04 [PATCH 00/13] tools: do cleanups related to libxc python bindings Juergen Gross
2015-10-23 13:05 ` [PATCH 01/13] libxc: remove most of tools/libxc/xc_dom_compat_linux.c Juergen Gross
2015-10-23 13:05 ` [PATCH 02/13] libxc: remove xc_get_bit_size() from tools/libxc/xc_dom_compat_linux.c Juergen Gross
2015-10-23 13:05 ` [PATCH 03/13] python: remove flask related libxc python bindings Juergen Gross
2015-10-23 13:05 ` [PATCH 04/13] python: remove cpupool " Juergen Gross
2015-10-23 13:05 ` [PATCH 05/13] python: remove cpuid " Juergen Gross
2015-10-23 13:05 ` [PATCH 06/13] python: remove device " Juergen Gross
2015-10-23 13:05 ` [PATCH 07/13] python: remove scheduler " Juergen Gross
2015-10-23 13:05 ` [PATCH 08/13] python: remove unused memory " Juergen Gross
2015-10-23 13:05 ` [PATCH 09/13] python: remove domain handling " Juergen Gross
2015-10-23 13:05 ` [PATCH 10/13] python: remove vcpu " Juergen Gross
2015-10-23 13:05 ` [PATCH 11/13] python: remove hvm " Juergen Gross
2015-10-23 13:05 ` [PATCH 12/13] python: remove permission " Juergen Gross
2015-10-23 13:05 ` [PATCH 13/13] python: remove unused other " Juergen Gross
2015-10-26 17:34 ` [PATCH 00/13] tools: do cleanups related to " Wei Liu
2015-11-09 15:19 ` Juergen Gross
2015-11-12 13:01 ` Wei Liu
2015-11-16 12:09 ` Ian Campbell [this message]
2015-11-16 12:30 ` Juergen Gross
2015-11-16 12:37 ` 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=1447675761.27871.48.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.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.