From: Wei Liu <wei.liu2@citrix.com>
To: committers@xenproject.org
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>
Subject: Remaining patches for 4.7 and anticipated release date
Date: Tue, 7 Jun 2016 17:22:54 +0100 [thread overview]
Message-ID: <20160607162254.GQ25922@citrix.com> (raw)
Committers,
I have some patches outstanding. Here is the list:
1. xen/arm: build: add missed dependency for head.S (either v1 or v2)
2. x86/mce: handle reserved domain ID in XEN_MC_msrinject
3. Revert "x86/hvm: add support for pcommit instruction"
4. xen/serial: Fix incorrect length of strncmp for dtuar
We shall commit this by tomorrow.
Realistically I don't expect them to have impact on real world user. So
we can probably release after we get a push. Let's aim to release on
Friday or next Monday. Does this sound plausible?
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-06-07 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 16:22 Wei Liu [this message]
2016-06-07 16:43 ` Konrad Rzeszutek Wilk
2016-06-07 17:33 ` Wei Liu
2016-06-08 11:41 ` Wei Liu
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=20160607162254.GQ25922@citrix.com \
--to=wei.liu2@citrix.com \
--cc=committers@xenproject.org \
--cc=xen-devel@lists.xenproject.org \
--subject='Re: Remaining patches for 4.7 and anticipated release date' \
/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
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).