From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: Wei Liu <wei.liu2@citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH 2/6] tools/libx{l, c}: Remove the toolstack_{save, restore} callbacks
Date: Wed, 22 Jul 2015 12:07:29 +0100 [thread overview]
Message-ID: <55AF7971.2000205@citrix.com> (raw)
In-Reply-To: <1437560870.12884.7.camel@citrix.com>
On 22/07/15 11:27, Ian Campbell wrote:
> On Mon, 2015-07-20 at 11:37 +0100, Andrew Cooper wrote:
>> +TOOLSTACK (deprecated)
>> +----------------------
>> +
>> +> *This record was only present for transitionary purposes during
> "transitionary" isn't really a word... transitional is (even if it
> sounds a bit odd to me)?
It very much is.
http://www.oxforddictionaries.com/definition/english/transition
It is an appropriate derivative in this case.
>
>> +> development. It is should not be used.*
> Does it needs to be accepted on restore for N->N+1 purposes (or N+M for
> M>1 since you care about that)? Or does the conversion routine turn it
> into something else?
The libxc toolstack record was used in the #LIBXL_HVM_COMPAT phase, but
nothing (not even the conversion script) will generate one any more.
~Andrew
next prev parent reply other threads:[~2015-07-22 11:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 10:37 [PATCH for 4.6 0/6] Prune legacy migration and move migration v2 out of daft status Andrew Cooper
2015-07-20 10:37 ` [PATCH 1/6] tools/libxc: Remove legacy migration implementation Andrew Cooper
2015-07-22 10:25 ` Ian Campbell
2015-07-22 11:05 ` Andrew Cooper
2015-07-20 10:37 ` [PATCH 2/6] tools/libx{l, c}: Remove the toolstack_{save, restore} callbacks Andrew Cooper
2015-07-22 10:27 ` Ian Campbell
2015-07-22 11:07 ` Andrew Cooper [this message]
2015-07-22 11:14 ` Ian Campbell
2015-07-28 10:09 ` Ian Campbell
2015-07-20 10:37 ` [PATCH 3/6] tools/libx{l, c}: Remove XC_DEVICE_MODEL_RESTORE_FILE Andrew Cooper
2015-07-22 10:28 ` Ian Campbell
2015-07-20 10:37 ` [PATCH 4/6] tools/libx{l, c}: Drop '2' suffixes from xc_domain_{save, restore}2() functions Andrew Cooper
2015-07-22 10:29 ` Ian Campbell
2015-07-20 10:37 ` [PATCH 5/6] docs: Migration v2 is now no longer draft Andrew Cooper
2015-07-22 10:29 ` Ian Campbell
2015-07-20 10:37 ` [PATCH 6/6] tools/libx{l, c}: Fix trivial Coverity defects in migration v2 code Andrew Cooper
2015-07-22 10:31 ` Ian Campbell
2015-07-22 10:33 ` [PATCH for 4.6 0/6] Prune legacy migration and move migration v2 out of daft status Ian Campbell
2015-07-22 11:22 ` Wei Liu
2015-07-22 11:26 ` Andrew Cooper
2015-07-22 11:30 ` Wei Liu
2015-07-22 11:57 ` Andrew Cooper
2015-07-22 12:20 ` Wei Liu
2015-07-22 12:47 ` Yang Hongyang
2015-07-28 10:42 ` 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=55AF7971.2000205@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=ian.campbell@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.