All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Jan Beulich <JBeulich@suse.com>, Wei Liu <wei.liu2@citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: OVMF related osstest failures on multiple branches
Date: Thu, 7 Jan 2016 15:42:00 +0000	[thread overview]
Message-ID: <1452181320.21055.253.camel@citrix.com> (raw)
In-Reply-To: <22158.34297.854903.908862@mariner.uk.xensource.com>

On Thu, 2016-01-07 at 15:36 +0000, Ian Jackson wrote:
>  endif
> -OVMF_UPSTREAM_REVISION ?= cb9a7ebabcd6b8a49dc0854b2f9592d732b5afbd
> +OVMF_UPSTREAM_REVISION ?= af9785a9ed61daea52b47f0bf448f1f228beee1e

This should be:
 OVMF_UPSTREAM_REVISION ?= 52a99493cce88a9d4ec8a02d7f1bd1a1001ce60d

You've picked up 04c5efb0a141 but not f046e501bbc I think, we should take
both, since that's what I've tested if nothing else.

Ian.

>  QEMU_UPSTREAM_REVISION ?= qemu-xen-4.6.0
>  MINIOS_UPSTREAM_REVISION ?= xen-RELEASE-4.6.0
>  # Fri Jun 26 11:58:40 2015 +0100

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

  reply	other threads:[~2016-01-07 15:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06 12:35 OVMF related osstest failures on multiple branches Ian Campbell
2016-01-06 14:27 ` Ian Campbell
2016-01-06 15:28   ` Ian Campbell
2016-01-06 16:20     ` Jan Beulich
2016-01-06 16:28       ` Ian Jackson
2016-01-06 17:08         ` Ian Campbell
2016-01-06 17:14           ` Ian Jackson
2016-01-07 15:36             ` Ian Jackson
2016-01-07 15:42               ` Ian Campbell [this message]
2016-01-07 15:47                 ` Ian Jackson
2016-01-07 15:53                   ` Ian Jackson
2016-01-06 16:50     ` Wei Liu

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=1452181320.21055.253.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Stefano.Stabellini@eu.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.