From: "Gao, Liming" <liming.gao@intel.com>
To: "Wu, Hao A" <hao.a.wu@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Wu, Hao A" <hao.a.wu@intel.com>
Subject: Re: [PATCH 0/2] Handle input file of size 0 for GenFfs/GenSec tools
Date: Thu, 10 Nov 2016 05:05:53 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14B4B0373@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1478751738-16372-1-git-send-email-hao.a.wu@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Hao Wu
> Sent: Thursday, November 10, 2016 12:22 PM
> To: edk2-devel@lists.01.org
> Cc: Wu, Hao A <hao.a.wu@intel.com>; Gao, Liming <liming.gao@intel.com>
> Subject: [edk2] [PATCH 0/2] Handle input file of size 0 for GenFfs/GenSec
> tools
>
> The series enhances the logic in GenFfs and GenSec tool to handle input
> file of size 0 properly.
>
> Cc: Liming Gao <liming.gao@intel.com>
> Cc: Yonghong Zhu <yonghong.zhu@intel.com>
>
> Hao Wu (2):
> BaseTools/GenFfs: Fix return too early when input file is of size 0
> BaseTools/GenSec: Return correct status when input file size is 0
>
> BaseTools/Source/C/GenFfs/GenFfs.c | 11 +++++++++--
> BaseTools/Source/C/GenSec/GenSec.c | 16 +++++++++++-----
> 2 files changed, 20 insertions(+), 7 deletions(-)
>
> --
> 1.9.5.msysgit.0
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2016-11-10 5:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 4:22 [PATCH 0/2] Handle input file of size 0 for GenFfs/GenSec tools Hao Wu
2016-11-10 4:22 ` [PATCH 1/2] BaseTools/GenFfs: Fix return too early when input file is of size 0 Hao Wu
2016-11-10 4:22 ` [PATCH 2/2] BaseTools/GenSec: Return correct status when input file size is 0 Hao Wu
2016-11-10 5:05 ` Gao, Liming [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=4A89E2EF3DFEDB4C8BFDE51014F606A14B4B0373@shsmsx102.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