mirror of https://github.com/acidanthera/audk.git
BaseTools: Remove duplicated words in C tools
In an effort to clean the documentation of the above package, remove duplicated words. Cc: Bob Feng <bob.c.feng@intel.com> Cc: Liming Gao <gaoliming@byosoft.com.cn> Reviewed-by: Bob Feng <bob.c.feng@intel.com> Signed-off-by: Pierre Gondois <pierre.gondois@arm.com>
This commit is contained in:
parent
8fc06b6e19
commit
d618fe05bf
|
@ -91,7 +91,7 @@ Routine Description:
|
|||
|
||||
Arguments:
|
||||
|
||||
SourceFv - Address of the Fv in memory, this firmware volume volume will
|
||||
SourceFv - Address of the Fv in memory, this firmware volume will
|
||||
be modified, if SourceFfsFile exists
|
||||
SourceFfsFile - Input FFS file to replace
|
||||
|
||||
|
@ -141,7 +141,7 @@ Routine Description:
|
|||
|
||||
Arguments:
|
||||
|
||||
SourceFv - Address of the Fv in memory, this firmware volume volume will
|
||||
SourceFv - Address of the Fv in memory, this firmware volume will
|
||||
be modified, if SourceFfsFile exists
|
||||
SourceFfsFile - Input FFS file to replace
|
||||
|
||||
|
@ -285,7 +285,7 @@ Routine Description:
|
|||
|
||||
Arguments:
|
||||
|
||||
SourceFv - Address of the Fv in memory, this firmware volume volume will
|
||||
SourceFv - Address of the Fv in memory, this firmware volume will
|
||||
be modified, if SourceFfsFile exists
|
||||
SourceFfsFile - Input FFS file to replace
|
||||
|
||||
|
|
|
@ -37,7 +37,7 @@ CONST EFI_DEVICE_PATH_PROTOCOL mUefiDevicePathLibEndDevicePath = {
|
|||
@retval TRUE DevicePath is valid.
|
||||
@retval FALSE DevicePath is NULL.
|
||||
@retval FALSE Maxsize is less than sizeof(EFI_DEVICE_PATH_PROTOCOL).
|
||||
@retval FALSE The length of any node node in the DevicePath is less
|
||||
@retval FALSE The length of any node in the DevicePath is less
|
||||
than sizeof (EFI_DEVICE_PATH_PROTOCOL).
|
||||
@retval FALSE If MaxSize is not zero, the size of the DevicePath
|
||||
exceeds MaxSize.
|
||||
|
|
|
@ -299,7 +299,7 @@ Returns:
|
|||
return STATUS_ERROR;
|
||||
}
|
||||
if (TempNumber == 0) {
|
||||
Error (NULL, 0, 1003, "Invalid option value", "Fv block size can't be be set to zero");
|
||||
Error (NULL, 0, 1003, "Invalid option value", "Fv block size can't be set to zero");
|
||||
return STATUS_ERROR;
|
||||
}
|
||||
mFvDataInfo.FvBlocks[0].Length = (UINT32) TempNumber;
|
||||
|
|
|
@ -714,7 +714,7 @@ Tree *MR_compute_pred_tree_ctxXX(p)
|
|||
if (p == NULL) return NULL;
|
||||
|
||||
/* this appears strange: why do we OR the context
|
||||
of and AND predicate ? It is because of the way
|
||||
of an AND predicate ? It is because of the way
|
||||
that predicates are evaluated: if the context is
|
||||
wrong then it's the same as if the predicate was
|
||||
true. That means that even when one leg of an
|
||||
|
@ -1531,7 +1531,7 @@ Predicate * MR_find_in_aSubBlk(alt)
|
|||
* 1. if lookahead for alt i is contained in the lookahead for any
|
||||
* alt j then ignore semantic predicate of alt i
|
||||
* 2. if lookahead for alt i is not contained in the lookahead for
|
||||
* any alt j then add add predicate i to the OR list to be hoisted
|
||||
* any alt j then add predicate i to the OR list to be hoisted
|
||||
* 3. if lookahead for alt i overlaps the lookahead for some alt j then
|
||||
* add a dummy semantic predicate for alt j
|
||||
*
|
||||
|
|
Loading…
Reference in New Issue