From: "Zhu, Yonghong" <yonghong.zhu@intel.com>
To: "Wu, Hao A" <hao.a.wu@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Gao, Liming" <liming.gao@intel.com>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [PATCH 0/3] BaseTools/Source/C: Fix VS2010/2012 build failure
Date: Mon, 6 Mar 2017 05:18:18 +0000 [thread overview]
Message-ID: <B9726D6DCCFB8B4CA276A9169B02216D51E20DCE@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20170306051041.25480-1-hao.a.wu@intel.com>
Looks good.
Reviewed-by: Yonghong Zhu <yonghong.zhu@intel.com>
Best Regards,
Zhu Yonghong
-----Original Message-----
From: Wu, Hao A
Sent: Monday, March 6, 2017 1:11 PM
To: edk2-devel@lists.01.org
Cc: Wu, Hao A <hao.a.wu@intel.com>; Zhu, Yonghong <yonghong.zhu@intel.com>; Gao, Liming <liming.gao@intel.com>
Subject: [PATCH 0/3] BaseTools/Source/C: Fix VS2010/2012 build failure
https://bugzilla.tianocore.org/show_bug.cgi?id=417
The series resolves the build failure for the VS2010/2012 build failure for BaseTools GenFw, GenVtf & VolInfo source codes.
Cc: Yonghong Zhu <yonghong.zhu@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
Hao Wu (3):
BaseTools/GenFw: Fix VS2010/VS2012 build failure
BaseTools/GenVtf: Fix VS2010/VS2012 build failure
BaseTools/VolInfo: Fix VS2010/VS2012 build failure
BaseTools/Source/C/GenFw/Elf32Convert.c | 17 ++++++++++------- BaseTools/Source/C/GenFw/Elf64Convert.c | 17 ++++++++++-------
BaseTools/Source/C/GenVtf/GenVtf.c | 6 ++++--
BaseTools/Source/C/VolInfo/VolInfo.c | 4 +++-
4 files changed, 27 insertions(+), 17 deletions(-)
--
2.12.0.windows.1
prev parent reply other threads:[~2017-03-06 5:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 5:10 [PATCH 0/3] BaseTools/Source/C: Fix VS2010/2012 build failure Hao Wu
2017-03-06 5:10 ` [PATCH 1/3] BaseTools/GenFw: Fix VS2010/VS2012 " Hao Wu
2017-03-06 5:10 ` [PATCH 2/3] BaseTools/GenVtf: " Hao Wu
2017-03-06 5:10 ` [PATCH 3/3] BaseTools/VolInfo: " Hao Wu
2017-03-06 5:18 ` Zhu, Yonghong [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=B9726D6DCCFB8B4CA276A9169B02216D51E20DCE@SHSMSX103.ccr.corp.intel.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