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>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: 4.7.2 / 4.6.5 preparations
Date: Thu, 9 Feb 2017 10:26:48 +0000	[thread overview]
Message-ID: <a34d26f8-2c04-b5d3-152f-e8a457b27f6e@citrix.com> (raw)
In-Reply-To: <589C4A0102000078001381E8@prv-mh.provo.novell.com>

On 09/02/17 09:52, Jan Beulich wrote:
> All,
>
> these stable releases are due in about 3 weeks time. Please indicate
> backports you consider necessary but find still missing. Commits
> already marked for backporting:
>
> e719192026 xen: credit2: never consider CPUs outside of our cpupool.
> (for 4.7.5 only, unless anyone cares to also provide 4.6 backports of
> not just this, but also 548db87428 and 7478ebe160+ad5808d905, if
> applicable in the first place)
>
> 30921dc2df x86/ept: allow write-combining on !mfn_valid() MMIO mappings again

Neither are functional fixes, but d0fd9ae54491 and d45fae589b8d are both
useful as extra information.  (Both of these patches originated because
of an absence of information in customer bug reports.)

~Andrew

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

  parent reply	other threads:[~2017-02-09 10:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09  9:52 4.7.2 / 4.6.5 preparations Jan Beulich
2017-02-09 10:00 ` Wei Liu
2017-02-09 10:26 ` Andrew Cooper [this message]
2017-02-20 14:08   ` 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=a34d26f8-2c04-b5d3-152f-e8a457b27f6e@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.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).