/** @file\r
- DXE Dispatcher Dependency Evaluator\r
+ DXE Dispatcher Dependency Evaluator.\r
\r
This routine evaluates a dependency expression (DEPENDENCY_EXPRESSION) to determine\r
if a driver can be scheduled for execution. The criteria for\r
Grow size of the Depex stack\r
\r
@retval EFI_SUCCESS Stack successfully growed. \r
- @retval EFI_OUT_OF_RESOURCES There is not enough system memory to grow the \r
- stack.\r
+ @retval EFI_OUT_OF_RESOURCES There is not enough system memory to grow the stack.\r
\r
**/\r
EFI_STATUS\r
\r
\r
/**\r
- Push an element onto the Boolean Stack\r
+ Push an element onto the Boolean Stack.\r
\r
@param Value BOOLEAN to push. \r
\r
@retval EFI_SUCCESS The value was pushed onto the stack. \r
- @retval EFI_OUT_OF_RESOURCES There is not enough system memory to grow the \r
- stack.\r
+ @retval EFI_OUT_OF_RESOURCES There is not enough system memory to grow the stack.\r
\r
**/\r
EFI_STATUS\r
@param Value BOOLEAN to pop. \r
\r
@retval EFI_SUCCESS The value was popped onto the stack. \r
- @retval EFI_ACCESS_DENIED The pop operation underflowed the stack\r
+ @retval EFI_ACCESS_DENIED The pop operation underflowed the stack.\r
\r
**/\r
EFI_STATUS \r
it will be cleared by CoreSchedule(), and then the driver can be\r
dispatched.\r
\r
- @param DriverEntry DriverEntry element to update \r
+ @param DriverEntry DriverEntry element to update .\r
\r
@retval EFI_SUCCESS It always works.\r
\r
routine in this case. The SOR is just ignored and is a nop in the grammer.\r
POSTFIX means all the math is done on top of the stack.\r
\r
- @param DriverEntry DriverEntry element to update \r
+ @param DriverEntry DriverEntry element to update. \r
\r
@retval TRUE If driver is ready to run. \r
@retval FALSE If driver is not ready to run or some fatal error \r
\r
//\r
// Clean out memory leaks in Depex Boolean stack. Leaks are only caused by\r
- // incorrectly formed DEPEX expressions\r
+ // incorrectly formed DEPEX expressions\r
//\r
mDepexEvaluationStackPointer = mDepexEvaluationStack;\r
\r