From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Christian Lindig <christian.lindig@citrix.com>
Cc: Juergen Gross <jgross@suse.com>, Wei Liu <wei.liu2@citrix.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>,
Jim Fehlig <jfehlig@suse.com>, David Scott <dave@recoil.org>,
Ian Jackson <Ian.Jackson@citrix.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH RFC] tools: Drop xc_cpuid_check() and bindings
Date: Tue, 18 Jul 2017 22:56:21 +0200 [thread overview]
Message-ID: <20170718205621.GZ1095@mail-itl> (raw)
In-Reply-To: <3C0480BD-21AC-481E-B4BD-66C0E96AE79C@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 702 bytes --]
On Mon, Jul 17, 2017 at 01:54:19PM +0000, Christian Lindig wrote:
>
> > On 17. Jul 2017, at 13:38, Andrew Cooper <Andrew.Cooper3@citrix.com> wrote:
> >
> > It turns out that Xapi has a library function using it, but that
> > function is dead so can be removed.
>
> I am fine with the removal of the OCaml bindings and the patch for the OCaml code. If the code is fundamentally broken it should be removed in any case but like you already said, we are not aware of any clients.
Same for python bindings.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-18 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 12:38 [PATCH RFC] tools: Drop xc_cpuid_check() and bindings Andrew Cooper
2017-07-17 13:54 ` Christian Lindig
2017-07-18 20:56 ` Marek Marczykowski-Górecki [this message]
2017-07-19 10:32 ` Wei Liu
2017-07-19 10:43 ` Juergen Gross
2017-07-19 12:50 ` Boris Ostrovsky
2017-07-20 16:36 ` 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=20170718205621.GZ1095@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=christian.lindig@citrix.com \
--cc=dave@recoil.org \
--cc=jfehlig@suse.com \
--cc=jgross@suse.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 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).