xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: anthony.perard@citrix.com, xen-devel@lists.xensource.com
Subject: Re: [lersek@redhat.com: Re: [PATCH v3] OvmfPkg/build.sh: Make GCC5 the default toolchain, catch GCC43 and earlier]
Date: Fri, 25 Nov 2016 12:04:05 -0500	[thread overview]
Message-ID: <20161125170405.GA5299@char.us.oracle.com> (raw)
In-Reply-To: <20161125135156.GD11640@citrix.com>

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.


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

  reply	other threads:[~2016-11-25 17:04 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 [this message]
2016-11-29  4:34     ` Wei Liu
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=20161125170405.GA5299@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=anthony.perard@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 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).