From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH 0/2] Open Xen 4.9-unstable, reenable debug
Date: Fri, 2 Dec 2016 12:22:59 +0000 [thread overview]
Message-ID: <1480681381-1188-1-git-send-email-ian.jackson@eu.citrix.com> (raw)
I have pushed the first of these two patches to new-staging. It is
very like all previous such commits. The second, to reenable
hypervisor debug, I decided to get some review on.
When staging is properly open, I or the release manager will send an
announcement about its status and what should and should not be
committed where.
Thanks,
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-12-02 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 12:22 Ian Jackson [this message]
2016-12-02 12:23 ` [PATCH 1/2] Open Xen 4.9-unstable Ian Jackson
2016-12-02 12:53 ` Andrew Cooper
2016-12-02 12:23 ` [PATCH 2/2] Re-enable hypervisor debug as part of opening 4.9 Ian Jackson
2016-12-02 12:46 ` Jan Beulich
2016-12-02 12:51 ` Ian Jackson
2016-12-02 13:18 ` [PATCH 0/2] Open Xen 4.9-unstable, reenable debug Olaf Hering
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=1480681381-1188-1-git-send-email-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).