From: "Ni, Ruiyu" <ruiyu.ni@intel.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Patch] Nt32Pkg FDF: Move StatusCode Handler run earlier in DXE phase
Date: Sun, 22 Jan 2017 05:51:12 +0000 [thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5B885F23@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1484904535-9252-1-git-send-email-liming.gao@intel.com>
Reviewed-by: Ruiyu Ni <ruiyu.ni@intel.com>
Thanks/Ray
> -----Original Message-----
> From: Gao, Liming
> Sent: Friday, January 20, 2017 5:29 PM
> To: edk2-devel@lists.01.org
> Cc: Ni, Ruiyu <ruiyu.ni@intel.com>
> Subject: [Patch] Nt32Pkg FDF: Move StatusCode Handler run earlier in DXE
> phase
>
> Add StatusCode Handler into APRIORI DXE so that they can run early, then
> more DEBUG message can print.
>
> Cc: Ruiyu Ni <ruiyu.ni@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Liming Gao <liming.gao@intel.com>
> ---
> Nt32Pkg/Nt32Pkg.fdf | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Nt32Pkg/Nt32Pkg.fdf b/Nt32Pkg/Nt32Pkg.fdf index
> c198d73..4b5e03f 100644
> --- a/Nt32Pkg/Nt32Pkg.fdf
> +++ b/Nt32Pkg/Nt32Pkg.fdf
> @@ -171,6 +171,9 @@ APRIORI DXE {
> INF MdeModulePkg/Universal/DevicePathDxe/DevicePathDxe.inf
> INF MdeModulePkg/Universal/PCD/Dxe/Pcd.inf
> INF Nt32Pkg/MetronomeDxe/MetronomeDxe.inf
> + INF
> +
> MdeModulePkg/Universal/ReportStatusCodeRouter/RuntimeDxe/ReportSt
> atusC
> + odeRouterRuntimeDxe.inf INF
> +
> MdeModulePkg/Universal/StatusCodeHandler/RuntimeDxe/StatusCodeHan
> dlerR
> + untimeDxe.inf INF
> +
> Nt32Pkg/WinNtOemHookStatusCodeHandlerDxe/WinNtOemHookStatusCod
> eHandler
> + Dxe.inf
> }
>
> INF MdeModulePkg/Core/Pei/PeiMain.inf
> --
> 2.8.0.windows.1
prev parent reply other threads:[~2017-01-22 5:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 9:28 [Patch] Nt32Pkg FDF: Move StatusCode Handler run earlier in DXE phase Liming Gao
2017-01-22 5:51 ` Ni, Ruiyu [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=734D49CCEBEEF84792F5B80ED585239D5B885F23@SHSMSX104.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