summaryrefslogtreecommitdiffstats
path: root/MdePkg/Library/PeiPiLib
diff options
context:
space:
mode:
authoreric_tian <eric_tian@6f19259b-4bc3-4df7-8a09-765794883524>2008-09-16 06:13:42 +0000
committereric_tian <eric_tian@6f19259b-4bc3-4df7-8a09-765794883524>2008-09-16 06:13:42 +0000
commitf944ec32e7e1ccc2968838da946bf4fba4cc7bce (patch)
treef1ced41362c81dbfe7812988af137045654c68a7 /MdePkg/Library/PeiPiLib
parentf73e0ad215de60ef1f3b1fac6b5c880da38edef0 (diff)
downloadedk2-f944ec32e7e1ccc2968838da946bf4fba4cc7bce.tar.gz
edk2-f944ec32e7e1ccc2968838da946bf4fba4cc7bce.tar.bz2
edk2-f944ec32e7e1ccc2968838da946bf4fba4cc7bce.zip
follow up code review
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@5894 6f19259b-4bc3-4df7-8a09-765794883524
Diffstat (limited to 'MdePkg/Library/PeiPiLib')
-rw-r--r--MdePkg/Library/PeiPiLib/PeiPiLib.c36
1 files changed, 18 insertions, 18 deletions
diff --git a/MdePkg/Library/PeiPiLib/PeiPiLib.c b/MdePkg/Library/PeiPiLib/PeiPiLib.c
index 4c9cea865c..876f5cab39 100644
--- a/MdePkg/Library/PeiPiLib/PeiPiLib.c
+++ b/MdePkg/Library/PeiPiLib/PeiPiLib.c
@@ -32,26 +32,26 @@ CONST EFI_PEI_PPI_DESCRIPTOR mPpiListTemplate [] = {
};
/**
- Install a EFI_PEI_FIRMWARE_VOLUME_INFO PPI to inform PEI core about the existence of a new Firmware Volume.
+ Install a EFI_PEI_FIRMWARE_VOLUME_INFO PPI to inform PEI core about the existence of a new Firmware Volume.
- The function allocate the EFI_PEI_PPI_DESCRIPTOR structure and update the fields accordingly to parameter passed
- in and install the PPI.
-
- @param FvFormat Unique identifier of the format of the memory-mapped firmware volume. If NULL is specified,
- EFI_FIRMWARE_FILE_SYSTEM2_GUID is used as the Format GUID.
- @param FvInfo Points to a buffer which allows the EFI_PEI_FIRMWARE_VOLUME_PPI to
- process the volume. The format of this buffer is specific to the FvFormat. For
- memory-mapped firmware volumes, this typically points to the first byte of the
- firmware volume.
- @param FvInfoSize Size of the data provided by FvInfo. For memory-mapped firmware volumes, this is
- typically the size of the firmware volume.
- @param ParentFvName If the firmware volume originally came from a firmware file, then these point to the
- parent firmware volume name. If it did not originally come
- from a firmware file, these should be NULL.
- @param ParentFileName If the firmware volume originally came from a firmware file, then these point to the
- firmware volume file. If it did not originally come
- from a firmware file, these should be NULL.
+ The function allocate the EFI_PEI_PPI_DESCRIPTOR structure and update the fields accordingly to parameter passed
+ in and install the PPI.
+ @param FvFormat Unique identifier of the format of the memory-mapped firmware volume.
+ If NULL is specified, EFI_FIRMWARE_FILE_SYSTEM2_GUID is used as the Format GUID.
+ @param FvInfo Points to a buffer which allows the EFI_PEI_FIRMWARE_VOLUME_PPI to
+ process the volume. The format of this buffer is specific to the FvFormat. For
+ memory-mapped firmware volumes, this typically points to the first byte of the
+ firmware volume.
+ @param FvInfoSize Size of the data provided by FvInfo. For memory-mapped firmware volumes, this is
+ typically the size of the firmware volume.
+ @param ParentFvName If the firmware volume originally came from a firmware file, then these point to the
+ parent firmware volume name. If it did not originally come from a firmware file,
+ these should be NULL.
+ @param ParentFileName If the firmware volume originally came from a firmware file, then these point to the
+ firmware volume file. If it did not originally come from a firmware file,
+ these should be NULL.
+
**/
VOID
EFIAPI