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/2] DP: Link DxeSmmPerformanceLib to make DP command generic
Date: Wed, 1 Mar 2017 08:20:59 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14D6E6715@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1488354783-13920-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 01, 2017 3:53 PM
>To: edk2-devel@lists.01.org
>Cc: Zeng, Star <star.zeng@intel.com>
>Subject: [edk2] [PATCH 0/2] DP: Link DxeSmmPerformanceLib to make DP
>command generic
>
>Current PerformancePkg is linking DxePerformanceLib
>that could only dump PEI and DXE performance log.
>Current ShellPkg is linking BasePerformanceLibNull.
>
>We could link DxeSmmPerformanceLib to make DP command
>built from PerformancePkg and ShellPkg generic.
>
>Star Zeng (2):
> PerformancePkg: Link DxeSmmPerformanceLib to make DP command
>generic
> ShellPkg: Link DxeSmmPerformanceLib to make DP command generic
>
> PerformancePkg/PerformancePkg.dsc | 21 ++-------------------
> ShellPkg/ShellPkg.dsc | 2 +-
> 2 files changed, 3 insertions(+), 20 deletions(-)
>
>--
>2.8.1.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-01 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 7:53 [PATCH 0/2] DP: Link DxeSmmPerformanceLib to make DP command generic Star Zeng
2017-03-01 7:53 ` [PATCH 1/2] PerformancePkg: " Star Zeng
2017-03-01 7:53 ` [PATCH 2/2] ShellPkg: " Star Zeng
2017-03-01 7:56 ` Ni, Ruiyu
2017-03-01 21:12 ` Carsey, Jaben
2017-03-01 8:20 ` 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=4A89E2EF3DFEDB4C8BFDE51014F606A14D6E6715@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