xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Ian Campbell <ian.campbell@citrix.com>, Wei Liu <wei.liu2@citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: Stable backport request for new OVMF version
Date: Fri, 24 Jul 2015 02:09:17 -0600	[thread overview]
Message-ID: <55B20ECD0200007800094FC0@prv-mh.provo.novell.com> (raw)
In-Reply-To: <20150724075647.GD6750@zion.uk.xensource.com>

>>> On 24.07.15 at 09:56, <wei.liu2@citrix.com> wrote:
> On Fri, Jul 24, 2015 at 01:47:41AM -0600, Jan Beulich wrote:
>> >>> On 23.07.15 at 18:23, <ian.campbell@citrix.com> wrote:
>> > On Thu, 2015-07-23 at 10:11 -0600, Jan Beulich wrote:
>> >> > 
>> >> > > > On 23.07.15 at 17:59, <ian.campbell@citrix.com> wrote:
>> >> > On Thu, 2015-07-23 at 09:37 -0600, Jan Beulich wrote:
>> >> > > > 
>> >> > > > It's marked as experimental, not supported and not built by 
>> >> > > > default 
>> >> > > > --
>> >> > > > if that makes you feel more comfortable.
>> >> > > 
>> >> > > It does. So Ian, feel free to go ahead.
>> >> > 
>> >> > Thanks. I suppose you were addressing Ian J here since I don't
>> >> > typically do stable release work.
>> >> 
>> >> No, since this was mainly for ARM (for which I recall you doing
>> >> backports), I did indeed mean you.
>> > 
>> > OVMF isn't for ARM, it's x86.
>> > 
>> > I don't think we build OVMF for ARM under any circumstances. (I was
>> > hoping to add that to raisin at some point, but that's another story)
>> 
>> But didn't you say it's a prereq for ARM64? Or was that only
>> implicitly through the intended Debian update?
>> 
> 
> The prerequisite for ARM64 (in fact, running ARM64 test case in OSSTest)
> is OSSTest needs to upgrade to Debian Jessie. Ian wasn't clear about
> that in his reply. :-)

So what we really want is a backport of b28da5fc1c + 28e5d9a9ad.

Ian - is this needed on 4.4 and 4.5, or just the latter?

Jan

  reply	other threads:[~2015-07-24  8:09 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 ` Stable backport request for new OVMF version Ian Campbell
2015-07-23 14:26 ` 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 [this message]
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=55B20ECD0200007800094FC0@prv-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=ian.campbell@citrix.com \
    --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).