From: "Gao, Liming" <liming.gao@intel.com>
To: "Zeng, Star" <star.zeng@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Zeng, Star" <star.zeng@intel.com>
Subject: Re: [PATCH 0/3] DP: Handle "/" separator in debug path for GCC
Date: Wed, 15 Mar 2017 06:53:32 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14D6F024D@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1489557032-4064-1-git-send-email-star.zeng@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 Star Zeng
> Sent: Wednesday, March 15, 2017 1:50 PM
> To: edk2-devel@lists.01.org
> Cc: Zeng, Star <star.zeng@intel.com>
> Subject: [edk2] [PATCH 0/3] DP: Handle "/" separator in debug path for GCC
>
> Star Zeng (3):
> PerformancePkg Dp_App: Handle "/" separator in debug path for GCC
> build
> ShellPkg UefiDpLib: Handle "/" separator in debug path for GCC build
> MdeModulePkg BmPerf: Handle "/" separator in debug path for GCC build
>
> MdeModulePkg/Library/UefiBootManagerLib/BmPerformance.c | 4 ++--
> PerformancePkg/Dp_App/DpUtilities.c | 2 +-
> ShellPkg/Library/UefiDpLib/DpUtilities.c | 2 +-
> 3 files changed, 4 insertions(+), 4 deletions(-)
>
> --
> 2.7.0.windows.1
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-03-15 6:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 5:50 [PATCH 0/3] DP: Handle "/" separator in debug path for GCC Star Zeng
2017-03-15 5:50 ` [PATCH 1/3] PerformancePkg Dp_App: Handle "/" separator in debug path for GCC build Star Zeng
2017-03-15 5:50 ` [PATCH 2/3] ShellPkg UefiDpLib: " Star Zeng
2017-03-15 9:22 ` Ni, Ruiyu
2017-03-15 5:50 ` [PATCH 3/3] MdeModulePkg BmPerf: " Star Zeng
2017-03-15 5:52 ` Tian, Feng
2017-03-15 9:22 ` Ni, Ruiyu
2017-03-15 6:53 ` 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=4A89E2EF3DFEDB4C8BFDE51014F606A14D6F024D@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