xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Clark <christopher.w.clark@gmail.com>
To: Lars Kurth <lars.kurth@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>,
	Ian Jackson <Ian.Jackson@citrix.com>
Subject: Re: preparations for 4.9.1 and 4.7.4
Date: Thu, 12 Oct 2017 11:39:25 -0700	[thread overview]
Message-ID: <CACMJ4GZMEOB08nbRvygOfdpFi5X8XwOLG_rVC-K7rFnORkwLew@mail.gmail.com> (raw)
In-Reply-To: <0F867D1B-DBC6-4C3F-8431-AA0CC9155BF5@citrix.com>

On Fri, Oct 6, 2017 at 6:54 AM, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
> On 06/10/17 14:33, Jan Beulich wrote:
>> All,
>>
>> with the goal of releasing around the end of the month, please point
>> out backport candidates you find missing from the respective staging
>> branches, but which you consider relevant. Note that commits
>>
>> 1c2ea5ee05 x86/hvm/dmop: fix EFAULT condition
>> 4e383df865 x86/PV: fix/generalize guest nul selector handling
>
> dbc4b6e13a5 x86/msr: Correct the definition of MSR_IA32_APICBASE_BASE
> 3164f2f9db1 x86/svm: Fix a livelock when trying to run shadowed unpaged
> guests

88bfbf90e3 tools/libxc/xc_dom_arm: add missing variable initialization

thanks

Christopher

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-10-12 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06 13:33 preparations for 4.9.1 and 4.7.4 Jan Beulich
2017-10-06 13:54 ` Andrew Cooper
2017-10-09 14:17 ` Lars Kurth
2017-10-12 17:08 ` Lars Kurth
2017-10-12 18:39   ` Christopher Clark [this message]
2017-10-13  7:13   ` Jan Beulich
2017-10-13 11:45     ` Lars Kurth

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=CACMJ4GZMEOB08nbRvygOfdpFi5X8XwOLG_rVC-K7rFnORkwLew@mail.gmail.com \
    --to=christopher.w.clark@gmail.com \
    --cc=Ian.Jackson@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=lars.kurth@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=wei.liu2@citrix.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).