From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel List <xen-devel@lists.xen.org>,
George Dunlap <george.dunlap@eu.citrix.com>
Subject: (early) Xen-4.4-rc4 testing
Date: Mon, 17 Feb 2014 11:56:49 +0000 [thread overview]
Message-ID: <5301F901.6060202@citrix.com> (raw)
Hello,
Given an available testing slot over the weekend, I ran a XenRT nightly
on current staging (c/s 4e8d89bc1445f91c4c6c7bf0ad8d51b0c809841e, "pvh:
Fix regression due to assumption that HVM paths MUST use io-backend
device") which I took to be roughly Xen-4.4-rc4.
This testing included David Vrabels "x86/xen: allow privcmd hypercalls
to be preempted" kernel patch
I am happy to report that everything looks in shape. There are no new
problems compared to rc3.
~Andrew
reply other threads:[~2014-02-17 11:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5301F901.6060202@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=george.dunlap@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 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.