Code Scrub for Pcd, PlatformDriOverride and PlatOverMngr driver.

git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@6998 6f19259b-4bc3-4df7-8a09-765794883524

1 files changed, 7 insertions, 1 deletions

diff --git a/MdeModulePkg/Library/DxePlatDriOverLib/PlatDriOver.h b/MdeModulePkg/Library/DxePlatDriOverLib/PlatDriOver.h
index db2d6e5dab..50622b8bd3 100644
--- a/MdeModulePkg/Library/DxePlatDriOverLib/PlatDriOver.h
+++ b/MdeModulePkg/Library/DxePlatDriOverLib/PlatDriOver.h
@@ -70,7 +70,7 @@ typedef struct _DEVICE_PATH_STACK_ITEM{
 } DEVICE_PATH_STACK_ITEM;

 

 /**

-  Push a controller device path into a globle device path list

+  Push a controller device path into a globle device path list.

 

   @param  DevicePath     The controller device path to push into stack

 

@@ -114,6 +114,8 @@ CheckExistInStack (
   );

 

 /**

+  Update the FV file device path if it is not valid.

+

   According to a file GUID, check a Fv file device path is valid. If it is invalid,

   try to return the valid device path.

   FV address maybe changes for memory layout adjust from time to time, use this funciton

@@ -143,6 +145,8 @@ UpdateFvFileDevicePath (
   );

 

 /**

+  Gets the data and size of a variable.

+

   Read the EFI variable (VendorGuid/Name) and return a dynamically allocated

   buffer, and the size of the buffer. If failure return NULL.

 

@@ -165,6 +169,8 @@ GetVariableAndSize (
   );

 

 /**

+  Connect to the handle to a device on the device path.

+

   This function will create all handles associate with every device

   path node. If the handle associate with one device path node can not

   be created success, then still give one chance to do the dispatch,