From: Wei Liu <wei.liu2@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: anthony.perard@citrix.com, xen-devel@lists.xensource.com,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: [lersek@redhat.com: Re: [PATCH v3] OvmfPkg/build.sh: Make GCC5 the default toolchain, catch GCC43 and earlier]
Date: Tue, 29 Nov 2016 04:34:31 +0000 [thread overview]
Message-ID: <20161129043431.GJ11640@citrix.com> (raw)
In-Reply-To: <20161125170405.GA5299@char.us.oracle.com>
On Fri, Nov 25, 2016 at 12:04:05PM -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Nov 25, 2016 at 01:51:56PM +0000, Wei Liu wrote:
> > On Fri, Nov 25, 2016 at 08:24:00AM -0500, Konrad Rzeszutek Wilk wrote:
> > > Hey Wei, Anthony,
> > >
> > > Are you guys OK pushing this commit: 2667ad40919a in the
> > > git://xenbits.xen.org/ovmf.git
> > >
> > > tree? Without this I cannot build Xen 4.8 with TianoCore
> > > (--enable-ovmf).
> > >
> >
> > We normally don't deviate from upstream. We would need to wait for this
> > to pass osstest pushgate, and then update Config.mk.
>
> I see. We seem to be 791 commits behind upstream? Oh, and 770
> to catch up with 2667ad40919a. Yikes.
>
I see that commit has passed our pushgate. I will see what I can do.
In any case, because OVMF is still experimental and disabled by default,
we used to update the commit id in stable branches as well. So they will
get the latest commit at the end.
Or you can provide a custom tree when building Xen. There isn't really
anything that would tie OVMF to a specific version of Xen -- at least
not for now.
What is even better is that you can provide a OVMF binary direct via
toolstack in this release.
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-29 4:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 13:24 [lersek@redhat.com: Re: [PATCH v3] OvmfPkg/build.sh: Make GCC5 the default toolchain, catch GCC43 and earlier] Konrad Rzeszutek Wilk
2016-11-25 13:51 ` Wei Liu
2016-11-25 17:04 ` Konrad Rzeszutek Wilk
2016-11-29 4:34 ` Wei Liu [this message]
2016-11-28 12:38 ` Anthony PERARD
2016-11-28 15:03 ` Konrad Rzeszutek Wilk
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=20161129043431.GJ11640@citrix.com \
--to=wei.liu2@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=konrad.wilk@oracle.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).