From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Anthony Perard <anthony.perard@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: Stable backport request for new OVMF version
Date: Thu, 23 Jul 2015 15:19:35 +0100 [thread overview]
Message-ID: <1437661175.24746.3.camel@citrix.com> (raw)
In-Reply-To: <1437659800.19412.104.camel@citrix.com>
Forgot to CC the list, now done...
On Thu, 2015-07-23 at 14:56 +0100, Ian Campbell wrote:
> The version of OVMF in 4.5 (and presumably earlier) doesn't build with
> the gcc in modern Linux distros (I noticed it with 4.9 from
> Debian/Jessie).
>
> I think we should update Config.mk:OVMF_UPSTREAM_REVISION to
> cb9a7ebabcd6b8a49dc0854b2f9592d732b5afbd in all stable branches. That
> version is the one currently in master.
>
> One aspect of the specific failure I've tripped over (Debian Jessie) is
> that it will be a blocker for updating osstest to using the new version
> of Debian on the test hosts, which in turn is a prerequisite for arm64
> support.
>
> Ian.
next parent reply other threads:[~2015-07-23 14:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1437659800.19412.104.camel@citrix.com>
2015-07-23 14:19 ` Ian Campbell [this message]
2015-07-23 14:26 ` Stable backport request for new OVMF version Jan Beulich
2015-07-23 14:43 ` Ian Campbell
2015-07-23 14:51 ` Jan Beulich
2015-07-23 14:58 ` Ian Campbell
2015-07-23 15:28 ` Jan Beulich
2015-07-23 15:31 ` Wei Liu
2015-07-23 15:37 ` Jan Beulich
2015-07-23 15:59 ` Ian Campbell
2015-07-23 16:11 ` Jan Beulich
2015-07-23 16:23 ` Ian Campbell
2015-07-24 7:47 ` Jan Beulich
2015-07-24 7:56 ` Wei Liu
2015-07-24 8:09 ` Jan Beulich
2015-07-24 8:50 ` Ian Campbell
2015-07-23 15:04 ` 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=1437661175.24746.3.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=anthony.perard@citrix.com \
--cc=wei.liu2@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.