xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: preparations for 4.4.1, 4.3.3, and 4.2.5
Date: Mon, 19 May 2014 15:23:09 +0100	[thread overview]
Message-ID: <537A13CD.2030702@citrix.com> (raw)
In-Reply-To: <537A2D640200007800013B4B@mail.emea.novell.com>

On 19/05/14 15:12, Jan Beulich wrote:
> All,
>
> with the aim of releasing 4.4.1 no later than 3 months after the original
> 4.4.0 release, and - in order to consolidate effort as well as to not
> exceed the 3 month step by too much - 4.3.3 and 4.2.5, please point
> out to the relevant maintainers any backport requests you may observe
> still missing but required on the respective branches.
>
> Please note that there's no need to nominate
>
> 99c03bc6 "Nested VMX: load current_vmcs only when it exists"
> a0708452 "x86/MCE: bypass uninitialized vcpu in vMCE injection"
>
> as they're already on my list of backports to be done before the
> RC1s for the branches they reasonably apply to.
>
> Please note further that 4.2.5 is expected to be the last xen.org
> managed release from the 4.2 branch.
>
> Thanks, Jan

>From the current XenServer patchqueue backports section.

Xen side fixes:

6d27a53, c7e35c6, 4c15a82: 3x RTC emulation fixes.  Windows XP/2003 are
still susceptible to falling into infinite loops under Xen 4.3 and 4.4
without these.

Tool side fixes:

c566ab6 "libxl: Fix error path in libxl_device_events_handler"
81b0305 "tools/libxl: Don't read off the end of tinfo[]"
d752158 "tools/pygrub: Fix error handling if no valid partitions are found"

~Andrew

  reply	other threads:[~2014-05-19 14:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5379E20E02000078000136E7@mail.emea.novell.com>
2014-05-19 14:12 ` preparations for 4.4.1, 4.3.3, and 4.2.5 Jan Beulich
2014-05-19 14:23   ` Andrew Cooper [this message]
2014-05-19 14:30     ` Ian Jackson
2014-05-19 20:14   ` Boris Ostrovsky
2014-05-20 12:28     ` Jan Beulich
2014-05-20 13:31       ` Boris Ostrovsky
2014-05-23 13:47         ` Jan Beulich
2014-05-21 15:03   ` Daniel Kiper
2014-05-21 15:12     ` Jan Beulich
2014-05-30 12:03       ` Daniel Kiper
2014-06-11 19:28         ` Daniel Kiper
2014-10-07 10:04           ` Daniel Kiper
2014-05-27  7:44   ` Olaf Hering
2014-05-27  8:23     ` Olaf Hering
2014-05-27  9:23     ` Jan Beulich
2014-06-25 10:29   ` Roger Pau Monné
2014-06-25 10:34     ` Roger Pau Monné
2014-06-25 10:37     ` Jan Beulich

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=537A13CD.2030702@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xenproject.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 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).