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>
Subject: Re: [PATCH] BaseTools/Pccts: Resolve GCC sting format mismatch build warning
Date: Thu, 22 Dec 2016 03:28:22 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14D6C324D@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1482370302-12572-1-git-send-email-hao.a.wu@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
> -----Original Message-----
> From: Wu, Hao A
> Sent: Thursday, December 22, 2016 9:32 AM
> To: edk2-devel@lists.01.org
> Cc: Wu, Hao A <hao.a.wu@intel.com>; Gao, Liming <liming.gao@intel.com>;
> Zhu, Yonghong <yonghong.zhu@intel.com>
> Subject: [PATCH] BaseTools/Pccts: Resolve GCC sting format mismatch build
> warning
>
> Cc: Liming Gao <liming.gao@intel.com>
> Cc: Yonghong Zhu <yonghong.zhu@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Hao Wu <hao.a.wu@intel.com>
> ---
> BaseTools/Source/C/VfrCompile/Pccts/support/set/set.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/BaseTools/Source/C/VfrCompile/Pccts/support/set/set.c
> b/BaseTools/Source/C/VfrCompile/Pccts/support/set/set.c
> index eb6fba7..6b9b510 100644
> --- a/BaseTools/Source/C/VfrCompile/Pccts/support/set/set.c
> +++ b/BaseTools/Source/C/VfrCompile/Pccts/support/set/set.c
> @@ -554,7 +554,7 @@ register char *s;
> static set a;
> register unsigned *p, *endp;
>
> - set_new(a, strlen(s));
> + set_new(a, (unsigned) strlen(s));
> p = a.setword;
> endp = &(a.setword[a.n]);
> do {
> --
> 1.9.5.msysgit.0
prev parent reply other threads:[~2016-12-22 3:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 1:31 [PATCH] BaseTools/Pccts: Resolve GCC sting format mismatch build warning Hao Wu
2016-12-22 3:28 ` 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=4A89E2EF3DFEDB4C8BFDE51014F606A14D6C324D@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