From: Ian Campbell <Ian.Campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Don Slutz <dslutz@verizon.com>,
Fabio Fantoni <fabio.fantoni@m2r.biz>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Anthony PERARD <anthony.perard@citrix.com>
Subject: Re: [PATCH] libxl: fix cirrus vga video memory setting with upstream qemu
Date: Fri, 9 May 2014 15:08:23 +0100 [thread overview]
Message-ID: <1399644503.561.29.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1405091456210.14596@kaball.uk.xensource.com>
On Fri, 2014-05-09 at 15:03 +0100, Stefano Stabellini wrote:
> Given that upstream QEMU with Xen 4.2 was a tech preview and that if I
> am not mistaken we don't maintain Xen 4.2 anymore, it should be OK to
> depend on QEMU >= 1.3.
Thanks for confirming.
> > An ack from you guys on this change would be appreciated.
>
> I think the change is OK but I wonder if we should write down somewhere,
> maybe in the 4.5 release notes or on the wiki, that we depend on QEMU >=
> 1.3.
I think the appropriate place is the README in a similar place to the
build dependencies. I suppose it needs to be worded as semioptional to
account for the fact that we supply one which is certainly OK.
> > It's also been proposed that we backport this to stable branches, how
> > far back would it be safe/acceptable for us to go with that?
> > [...]
>
> Anything newer than 4.2 should be OK.
Since, as you say, qemu-xen was preview in 4.2 I don't think backporting
fixes to it would be appropriate anyway, regardless of the support
status of 4.2 generally.
Thanks,
Ian.
next prev parent reply other threads:[~2014-05-09 14:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 12:16 [PATCH] libxl: fix cirrus vga video memory setting with upstream qemu Fabio Fantoni
2014-04-22 13:11 ` Ian Jackson
2014-04-22 13:21 ` Fabio Fantoni
2014-04-24 10:33 ` Fabio Fantoni
2014-05-02 9:11 ` Fabio Fantoni
2014-05-02 11:41 ` Ian Campbell
2014-05-02 19:44 ` Don Slutz
2014-05-02 20:04 ` Fabio Fantoni
2014-05-07 12:20 ` Fabio Fantoni
2014-05-08 10:10 ` Ian Campbell
2014-05-08 10:41 ` Fabio Fantoni
2014-05-08 11:33 ` Ian Campbell
2014-05-08 15:03 ` Fabio Fantoni
2014-05-08 15:19 ` Ian Campbell
2014-05-09 8:01 ` Fabio Fantoni
2014-05-09 9:09 ` Ian Campbell
2014-05-09 14:03 ` Stefano Stabellini
2014-05-09 14:08 ` Ian Campbell [this message]
2014-05-09 14:24 ` Fabio Fantoni
2014-05-09 14:48 ` Fabio Fantoni
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=1399644503.561.29.camel@kazak.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=dslutz@verizon.com \
--cc=fabio.fantoni@m2r.biz \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).