From: Ian Campbell <ian.campbell@citrix.com>
To: robert.hu@intel.com
Cc: "Pang, LongtaoX" <longtaox.pang@intel.com>,
ian.jackson@eu.citrix.com, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [osstest test] 56996: tolerable FAIL - PUSHED
Date: Mon, 25 May 2015 10:01:10 +0100 [thread overview]
Message-ID: <1432544470.5748.164.camel@citrix.com> (raw)
In-Reply-To: <1432524668.27440.10.camel@localhost>
On Mon, 2015-05-25 at 11:31 +0800, Robert Hu wrote:
> On Sun, 2015-05-24 at 14:55 +0100, Ian Campbell wrote:
> > Longtao & Robert,
> >
> > FYI This pass pushed the non-grub bits of the part of the series which I
> > applied on Friday into the production instance.
> Thanks Ian.
> We're to reassemble and send v11 patches comprised of previous 01/09,
> 02/09, 06/09, 07/09, 08/09, 09/09 based on nestedhvm-v10-pretest-reduced
> branch. Shall we include 'grub: remove patch to disable submenu from
> 20_linux_xen overlay' in our patch set as well?
Yes, please.
prev parent reply other threads:[~2015-05-25 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <osstest-56996-mainreport@xen.org>
2015-05-24 13:55 ` [osstest test] 56996: tolerable FAIL - PUSHED Ian Campbell
2015-05-25 3:31 ` Robert Hu
2015-05-25 9:01 ` Ian Campbell [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=1432544470.5748.164.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=longtaox.pang@intel.com \
--cc=robert.hu@intel.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.