From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Keir Fraser <keir.xen@gmail.com>,
Tim Deegan <Tim.Deegan@citrix.com>
Subject: Re: PVH domU patches....
Date: Thu, 1 Aug 2013 11:53:46 -0700 [thread overview]
Message-ID: <20130801115346.33705ae4@mantra.us.oracle.com> (raw)
In-Reply-To: <51FA2328.2090806@citrix.com>
On Thu, 1 Aug 2013 09:58:16 +0100
Andrew Cooper <andrew.cooper3@citrix.com> wrote:
> On 01/08/13 06:50, Keir Fraser wrote:
> > On 31/07/2013 22:43, "Mukesh Rathor" <mukesh.rathor@oracle.com>
> > wrote:
> >
> >> Hi,
> >>
> >> I noticed the PVH domU patches are still not merged. Just wanna
> >> make sure nothing from me is waited upon. Please let me know. The
> >> latest tree with Tim's acks are at:
> >>
> >> git clone git://oss.oracle.com/git/mrathor/xen.git .
> >> git checkout pvh.v10.acked-1
> >>
> >>
> >> Look forward to seeing them in the unstable tree soon :).
> > Jan has done the bulk of the review on these and deserves a final
> > say. He is on holiday until next week.
> >
> > -- Keir
>
> As for the tests I was running, I am happy to declare that there are
> no apparent regressions in PV / HVM operations as a result of the
> series.
>
> Therefore, a tentative
>
> PV-HVM-Regression-Tested-by: Andrew Cooper <andrew.cooper3@citrix.com>
Thanks Andrew for running regressions, appreciate your help. Glad
to hear no regressions, I was extra careful to make sure I don't affect
normal PV/HVM paths :).
thanks,
Mukesh
prev parent reply other threads:[~2013-08-01 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 21:43 PVH domU patches Mukesh Rathor
2013-08-01 5:50 ` Keir Fraser
2013-08-01 8:58 ` Andrew Cooper
2013-08-01 18:53 ` Mukesh Rathor [this message]
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=20130801115346.33705ae4@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Tim.Deegan@citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir.xen@gmail.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).