MdePkg: Clean up source files
1. Do not use tab characters 2. No trailing white space in one line 3. All files must end with CRLF Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Liming Gao <liming.gao@intel.com>
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
/** @file
|
||||
Entry point to a the PEI Core.
|
||||
|
||||
Copyright (c) 2006 - 2010, Intel Corporation. All rights reserved.<BR>
|
||||
Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>
|
||||
This program and the accompanying materials
|
||||
are licensed and made available under the terms and conditions of the BSD License
|
||||
which accompanies this distribution. The full text of the license may be found at
|
||||
@@ -39,35 +39,35 @@ WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.
|
||||
the PEI Services Table and the file handle for the PEI Core itself have been established.
|
||||
If ProcessModuleEntryPointList() returns, then ASSERT() and halt the system.
|
||||
|
||||
@param SecCoreData Points to a data structure containing information about the
|
||||
PEI core's operating environment, such as the size and
|
||||
location of temporary RAM, the stack location and the BFV
|
||||
@param SecCoreData Points to a data structure containing information about the
|
||||
PEI core's operating environment, such as the size and
|
||||
location of temporary RAM, the stack location and the BFV
|
||||
location.
|
||||
|
||||
@param PpiList Points to a list of one or more PPI descriptors to be
|
||||
installed initially by the PEI core. An empty PPI list
|
||||
consists of a single descriptor with the end-tag
|
||||
|
||||
@param PpiList Points to a list of one or more PPI descriptors to be
|
||||
installed initially by the PEI core. An empty PPI list
|
||||
consists of a single descriptor with the end-tag
|
||||
EFI_PEI_PPI_DESCRIPTOR_TERMINATE_LIST.
|
||||
As part of its initialization phase, the PEI Foundation will
|
||||
add these SEC-hosted PPIs to its PPI database, such that both
|
||||
the PEI Foundation and any modules can leverage the associated
|
||||
add these SEC-hosted PPIs to its PPI database, such that both
|
||||
the PEI Foundation and any modules can leverage the associated
|
||||
service calls and/or code in these early PPIs.
|
||||
|
||||
**/
|
||||
VOID
|
||||
EFIAPI
|
||||
EFIAPI
|
||||
_ModuleEntryPoint(
|
||||
IN CONST EFI_SEC_PEI_HAND_OFF *SecCoreData,
|
||||
IN CONST EFI_PEI_PPI_DESCRIPTOR *PpiList
|
||||
)
|
||||
{
|
||||
ProcessModuleEntryPointList (SecCoreData, PpiList, NULL);
|
||||
|
||||
|
||||
//
|
||||
// Should never return
|
||||
//
|
||||
ASSERT(FALSE);
|
||||
CpuDeadLoop ();
|
||||
CpuDeadLoop ();
|
||||
}
|
||||
|
||||
|
||||
@@ -78,15 +78,15 @@ _ModuleEntryPoint(
|
||||
|
||||
@param SecCoreData Points to a data structure containing information about the PEI core's
|
||||
operating environment, such as the size and location of temporary RAM,
|
||||
the stack location and the BFV location.
|
||||
the stack location and the BFV location.
|
||||
|
||||
@param PpiList Points to a list of one or more PPI descriptors to be installed
|
||||
initially by the PEI core. An empty PPI list consists of
|
||||
a single descriptor with the end-tag
|
||||
initially by the PEI core. An empty PPI list consists of
|
||||
a single descriptor with the end-tag
|
||||
EFI_PEI_PPI_DESCRIPTOR_TERMINATE_LIST.
|
||||
As part of its initialization phase, the PEI Foundation will
|
||||
add these SEC-hosted PPIs to its PPI database, such that both
|
||||
the PEI Foundationand any modules can leverage the associated
|
||||
As part of its initialization phase, the PEI Foundation will
|
||||
add these SEC-hosted PPIs to its PPI database, such that both
|
||||
the PEI Foundationand any modules can leverage the associated
|
||||
service calls and/or code in these early PPIs.
|
||||
|
||||
**/
|
||||
|
Reference in New Issue
Block a user