All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: anthony.perard@citrix.com, xen-devel@lists.xensource.com,
	Wei Liu <wei.liu2@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Xen 4.6, OVMF and arm64
Date: Wed, 14 Oct 2015 13:55:39 +0100	[thread overview]
Message-ID: <alpine.DEB.2.02.1510141355070.27957@kaball.uk.xensource.com> (raw)
In-Reply-To: <1444822709.23192.166.camel@citrix.com>

On Wed, 14 Oct 2015, Ian Campbell wrote:
> On Wed, 2015-10-14 at 12:29 +0100, Wei Liu wrote:
> > I can send a patch for Config.mk when the patch passed our tests.
> 
> For xen-unstable I think we should just move up to
>  http://xenbits.xen.org/gitweb/?p=osstest/ovmf.git;a=shortlog;h=refs/heads/xen-tested-master
> 
> We don't have any separate tests for ovmf in 4.6 (since there is currently
> no correpsonding git branch to even test, I think) so the only way to
> trigger those would be to backport a Config.mk change (again, I think).
 
Maybe we should have a separate tree/branch for ovmf 4.6? What if a bug
is found?

  reply	other threads:[~2015-10-14 12:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 11:25 Xen 4.6, OVMF and arm64 Stefano Stabellini
2015-10-14 11:29 ` Wei Liu
2015-10-14 11:30   ` Stefano Stabellini
2015-10-14 11:35     ` Wei Liu
2015-10-14 11:32   ` Wei Liu
2015-10-14 11:38   ` Ian Campbell
2015-10-14 12:55     ` Stefano Stabellini [this message]
2015-10-14 13:04       ` Wei Liu
2015-10-14 13:04         ` Stefano Stabellini
2015-10-14 13:24           ` Wei Liu
2015-10-14 13:35             ` Ian Campbell
2015-10-14 13:39               ` Wei Liu
2015-10-14 13:51               ` Stefano Stabellini
2015-10-14 14:10                 ` Ian Campbell
2015-10-14 14:11                   ` Stefano Stabellini
2015-10-14 14:25                     ` Ian Campbell
2015-10-14 13:05       ` Ian Campbell

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=alpine.DEB.2.02.1510141355070.27957@kaball.uk.xensource.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=wei.liu2@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 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.