xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Xen Devel <xen-devel@lists.xensource.com>
Cc: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
Subject: [PATCH 0/3] libflask merging in libxenctrl
Date: Tue, 22 Jun 2010 10:26:55 +0100	[thread overview]
Message-ID: <1277198818-27090-1-git-send-email-vincent.hanquez@eu.citrix.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 852 bytes --]

The following patch series fold libflask into libxenctrl.

The flask library is small, and putting everything in libxenctrl make
relying on flask functionalities in libxl easier.

libflask is left for compatibility purpose, but should be considered
deprecated, and remove in the near future. all flask_ symbols are now
xc_flask_ symbols in libxenctrl.

also remove some code duplication in the add_ and del_ calls.

Vincent Hanquez (3):
  merge libflask into libxenctrl
  remove some duplicated code by having helper add/del functions
  add flask capabilities in python xc bindings

 tools/libxc/xc_flask.c            |  357 +++++++++++++++++++++++++++++++++++++
 tools/libxc/xenctrl.h             |   26 +++
 tools/python/xen/lowlevel/xc/xc.c |  251 ++++++++++++++++++++++++++
 3 files changed, 634 insertions(+), 0 deletions(-)


[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

             reply	other threads:[~2010-06-22  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22  9:26 Vincent Hanquez [this message]
2010-06-22  9:26 ` [PATCH 1/3] merge libflask into libxenctrl Vincent Hanquez
2010-06-22  9:26 ` [PATCH 2/3] remove some duplicated code by having helper add/del functions Vincent Hanquez
2010-06-22  9:26 ` [PATCH 3/3] add flask capabilities in python xc bindings Vincent Hanquez
2010-06-22  9:50 ` [PATCH 0/3] libflask merging in libxenctrl Tim Deegan
2010-06-22 10:04   ` Tim Deegan

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=1277198818-27090-1-git-send-email-vincent.hanquez@eu.citrix.com \
    --to=vincent.hanquez@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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).