public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Anthony PERARD <anthony.perard@citrix.com>, edk2-devel@ml01.01.org
Cc: Jordan Justen <jordan.l.justen@intel.com>,
	"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [PATCH v2 0/2] Fix runtime issue in XenBusDxe when compiled with GCC 6.2
Date: Tue, 6 Dec 2016 18:10:14 +0100	[thread overview]
Message-ID: <b9bf482f-796f-f90e-16fd-dbc315d59489@redhat.com> (raw)
In-Reply-To: <20161206120325.1425-1-anthony.perard@citrix.com>

On 12/06/16 13:03, Anthony PERARD wrote:
> 
> 
> Anthony PERARD (2):
>   OvmfPkg/XenHypercallLib: Add EFIAPI
>   OvmfPkg/build.sh: Use GCC49 toolchains with GCC 6.[0-2]
> 
>  OvmfPkg/Include/Library/XenHypercallLib.h      | 3 +++
>  OvmfPkg/Library/XenHypercallLib/XenHypercall.c | 3 +++
>  OvmfPkg/build.sh                               | 2 +-
>  3 files changed, 7 insertions(+), 1 deletion(-)
> 

For patch #1:
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Build-tested-by: Laszlo Ersek <lersek@redhat.com>

(With "OvmfPkg/OvmfPkgX64.dsc" and "ArmVirtPkg/ArmVirtXen.dsc".)

For patch #2:
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Regression-tested-by: Laszlo Ersek <lersek@redhat.com>

(I still use gcc-4.8, on RHEL-7.)

Series pushed as 919278054f43..432f1d83f77a.

I also closed <https://bugzilla.tianocore.org/show_bug.cgi?id=281> as
RESOLVED|INVALID.

Thanks!
Laszlo


      parent reply	other threads:[~2016-12-06 17:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-06 12:03 [PATCH v2 0/2] Fix runtime issue in XenBusDxe when compiled with GCC 6.2 Anthony PERARD
2016-12-06 12:03 ` [PATCH v2 1/2] OvmfPkg/XenHypercallLib: Add EFIAPI Anthony PERARD
2016-12-06 12:03 ` [PATCH v2 2/2] OvmfPkg/build.sh: Use GCC49 toolchains with GCC 6.[0-2] Anthony PERARD
2016-12-06 17:10 ` Laszlo Ersek [this message]

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-list 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=b9bf482f-796f-f90e-16fd-dbc315d59489@redhat.com \
    --to=devel@edk2.groups.io \
    /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