From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Cc: ian.jackson@eu.citrix.com
Subject: Re: [PATCH] libxl: Remove libxl_tmem_destroy and associated xl command
Date: Mon, 16 Apr 2012 12:37:11 -0700 (PDT) [thread overview]
Message-ID: <86afad50-a6a2-4b10-b2e3-f675215d003d@default> (raw)
In-Reply-To: <bf46871ecfeee48a8685.1334588483@cosworth.uk.xensource.com>
> From: Ian Campbell [mailto:ian.campbell@citrix.com]
> Subject: [PATCH] libxl: Remove libxl_tmem_destroy and associated xl command
>
>
> Accordingly remove this interface from libxl and xl but don't touch libxc or
> the hypervisor.
>
> This is the only libxl_tmem_* function which might potentially have required
> conversion to be asynchronous and which therefore might have been a potential
> API stability concern.
>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Thanks for handling this!
Acked-by: Dan Magenheimer <dan.magenheimer@oracle.com>
next prev parent reply other threads:[~2012-04-16 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 15:01 [PATCH] libxl: Remove libxl_tmem_destroy and associated xl command Ian Campbell
2012-04-16 19:37 ` Dan Magenheimer [this message]
2012-04-24 16:35 ` Ian Jackson
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=86afad50-a6a2-4b10-b2e3-f675215d003d@default \
--to=dan.magenheimer@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.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).