From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xenproject.org, Keir@xen.org,
Ian.Jackson@eu.citrix.com,
George Dunlap <George.Dunlap@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [V4 PATCH 0/2]: PVH xen tools: tools changes to create PVH guest
Date: Thu, 12 Sep 2013 17:23:04 -0700 [thread overview]
Message-ID: <20130912172304.3145a178@mantra.us.oracle.com> (raw)
In-Reply-To: <1378975094.10076.18.camel@kazak.uk.xensource.com>
On Thu, 12 Sep 2013 09:38:14 +0100
Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Wed, 2013-09-11 at 16:22 -0700, Mukesh Rathor wrote:
> > Please find V4 tools changes for PVH. These were built on unstable
> > c/s: 546ba2f17008387cf9821df46e6dac04f0883a9b. Comment logs fixed
> > with '---'.
>
> These are both now acked but I don't think it makes much sense to
> actually apply them until the h/v side is ready (cc-ing some set of
> people who I think are involved in that).
>
> Perhaps you could append this to the h/v series and whoever applies
> that can just hoover up the lot?
FWIW, applying them would be harmless in the sense that guest
creation will fail but will not crash xen or anything...
thanks
Mukesh
next prev parent reply other threads:[~2013-09-13 0:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 23:22 [V4 PATCH 0/2]: PVH xen tools: tools changes to create PVH guest Mukesh Rathor
2013-09-11 23:22 ` [V4 PATCH 1/2] PVH xen tools: libxc changes to build a " Mukesh Rathor
2013-09-12 8:32 ` Ian Campbell
2013-09-11 23:22 ` [V4 PATCH 2/2] PVH xen tools: libxl changes to create " Mukesh Rathor
2013-09-12 8:38 ` [V4 PATCH 0/2]: PVH xen tools: tools changes to create " Ian Campbell
2013-09-12 8:52 ` Jan Beulich
2013-09-13 0:23 ` Mukesh Rathor [this message]
2013-09-13 8:28 ` 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=20130912172304.3145a178@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=George.Dunlap@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=Keir@xen.org \
--cc=xen-devel@lists.xenproject.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).