From: Keir Fraser <keir@xen.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: backport requests for 4.x-testing
Date: Thu, 29 Mar 2012 10:22:28 +0100 [thread overview]
Message-ID: <CB99E864.3CF82%keir@xen.org> (raw)
In-Reply-To: <20120324172757.GA29504@phenom.dumpdata.com>
On 24/03/2012 18:27, "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com> wrote:
> On Tue, Mar 06, 2012 at 11:04:13AM +0000, Andrew Cooper wrote:
>> On 06/03/12 10:13, Jan Beulich wrote:
>>> For a (hopefully soon) upcoming 4.1.3 and 4.0.4, may I ask to consider
>>> the following changesets from -unstable for backporting:
>
> And also these:
> 24140 tools: xend: tolerate empty state/*.xml
> 23412 libxc: xc_domain_set_memory_map, xc_get_machine_memory_map (x86, amd64
> only)
> 23632 libxc: Squash xc_e820.h (and delete) into xenctrl.h
> 23225 x86: make the pv-only e820 array be dynamic.
> 23426 libxl: Add support for passing in the host's E820 for PCI passthrough
> 23428 libxl: Add 'e820_host' option to config file.
> 23427 libxl: Convert E820_UNUSABLE and E820_RAM to E820_UNUSABLE as
> appropriate.
> 24013 x86,hvm: enable VCPUOP_register_vcpu_info op in hvm hypercall
Applied 23225 and 24013. The other, toolstack-related, patches I will leave
for a tools maintainer to ack or apply.
-- Keir
> which I've back-ported to 4.1 (please see attachments)
>
next prev parent reply other threads:[~2012-03-29 9:22 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 10:13 backport requests for 4.x-testing Jan Beulich
2012-03-06 10:38 ` Keir Fraser
2012-03-06 11:04 ` Andrew Cooper
2012-03-07 7:25 ` Roderick Colenbrander
2012-03-07 9:43 ` Keir Fraser
2012-03-13 16:50 ` Ian Jackson
2012-03-13 17:25 ` Teck Choon Giam
2012-03-13 17:52 ` Teck Choon Giam
2012-03-13 18:23 ` Teck Choon Giam
2012-03-14 10:03 ` Ian Jackson
2012-03-14 9:58 ` Ian Jackson
2012-03-14 11:37 ` Ian Jackson
2012-03-14 23:08 ` Teck Choon Giam
2012-03-19 14:22 ` Teck Choon Giam
2012-04-03 15:04 ` Ian Jackson
2012-03-07 9:43 ` Keir Fraser
2012-03-07 10:44 ` Andrew Cooper
2012-03-07 10:59 ` Keir Fraser
2012-03-07 11:06 ` Jan Beulich
2012-03-07 11:08 ` Andrew Cooper
2012-03-07 19:38 ` Ian Campbell
2012-03-08 10:38 ` Andrew Cooper
2012-03-08 10:42 ` Keir Fraser
2012-03-13 16:52 ` Ian Jackson
2012-03-24 17:27 ` Konrad Rzeszutek Wilk
2012-03-29 9:22 ` Keir Fraser [this message]
2012-03-29 11:32 ` Teck Choon Giam
2012-03-29 11:42 ` Teck Choon Giam
2012-03-29 15:11 ` Konrad Rzeszutek Wilk
2012-03-29 15:26 ` Teck Choon Giam
2012-03-29 15:56 ` Konrad Rzeszutek Wilk
2012-03-29 16:20 ` Teck Choon Giam
2012-03-29 16:23 ` Konrad Rzeszutek Wilk
2012-03-29 16:39 ` Teck Choon Giam
2012-03-29 11:55 ` Stefano Stabellini
2012-03-29 15:31 ` Jan Beulich
2012-03-29 17:06 ` Stefano Stabellini
2012-03-30 8:23 ` Keir Fraser
2012-03-30 9:59 ` Stefano Stabellini
2012-04-03 15:08 ` Ian Jackson
2012-04-03 15:15 ` Teck Choon Giam
2012-04-03 16:58 ` Ian Jackson
2012-04-03 19:50 ` Teck Choon Giam
2012-04-03 20:02 ` Teck Choon Giam
2012-04-04 10:22 ` Ian Jackson
2012-04-04 12:54 ` Teck Choon Giam
2012-04-04 15:09 ` Ian Jackson
2012-03-07 9:18 ` Keir Fraser
2012-03-07 10:10 ` Jan Beulich
2012-03-08 10:00 ` Jan Beulich
2012-03-08 10:05 ` Keir Fraser
2012-03-08 10:45 ` Jan Beulich
2012-03-08 11:00 ` Keir Fraser
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=CB99E864.3CF82%keir@xen.org \
--to=keir@xen.org \
--cc=andrew.cooper3@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.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).