[edk2-devel] [PATCH v2 1/7] EmulatorPkg: Fix various typos

Cœur coeur at gmx.fr
Tue Jul 2 16:40:21 UTC 2019


Fix various typos in EmulatorPkg.

Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Coeur <coeur at gmx.fr>
---
EmulatorPkg/CpuRuntimeDxe/MpService.c  | 11 +++++------
EmulatorPkg/EmuBlockIoDxe/EmuBlockIo.c | 14 +++++++-------
EmulatorPkg/EmuGopDxe/GopDriver.c      |  4 ++--
EmulatorPkg/EmuGopDxe/GopInput.c       | 12 ++++++------
EmulatorPkg/EmuGopDxe/GopScreen.c      |  6 +++---
EmulatorPkg/EmuThunkDxe/EmuThunk.c     |  2 +-
6 files changed, 24 insertions(+), 25 deletions(-)

diff --git a/EmulatorPkg/CpuRuntimeDxe/MpService.c b/EmulatorPkg/CpuRuntimeDxe/MpService.c
index 42f94ada27..ff379a1ce3 100644
--- a/EmulatorPkg/CpuRuntimeDxe/MpService.c
+++ b/EmulatorPkg/CpuRuntimeDxe/MpService.c
@@ -29,10 +29,9 @@
Diagnostics applications may also use this protocol for multi-processor.

Copyright (c) 2006 - 2012, Intel Corporation. All rights reserved.<BR>
-Portitions Copyright (c) 2011, Apple Inc. All rights reserved.
+Portions Copyright (c) 2011, Apple Inc. All rights reserved.
SPDX-License-Identifier: BSD-2-Clause-Patent

-
**/

#include "CpuDriver.h"
@@ -292,7 +291,7 @@ CpuMpServicesGetProcessorInfo (
and releases the BSP to continue with other tasks.
-# The caller can use the CheckEvent() and WaitForEvent() services to check
the state of the WaitEvent created in step 1.
-    -# When the APs complete their task or TimeoutInMicroSecondss expires, the MP
+    -# When the APs complete their task or TimeoutInMicroSeconds expires, the MP
Service signals WaitEvent by calling the EFI SignalEvent() function. If
FailedCpuList is not NULL, its content is available when WaitEvent is
signaled. If all APs returned from Procedure prior to the timeout, then
@@ -332,7 +331,7 @@ CpuMpServicesGetProcessorInfo (
EFI_EVENT is defined in CreateEvent() in
the Unified Extensible Firmware Interface
Specification.
-  @param[in]  TimeoutInMicrosecsond   Indicates the time limit in microseconds for
+  @param[in]  TimeoutInMicroseconds   Indicates the time limit in microseconds for
APs to return from Procedure, either for
blocking or non-blocking mode. Zero means
infinity.  If the timeout expires before
@@ -601,7 +600,7 @@ Done:
This function is used to dispatch one enabled AP to the function specified by
Procedure passing in the argument specified by ProcedureArgument.  If WaitEvent
is NULL, execution is in blocking mode. The BSP waits until the AP finishes or
-  TimeoutInMicroSecondss expires. Otherwise, execution is in non-blocking mode.
+  TimeoutInMicroSeconds expires. Otherwise, execution is in non-blocking mode.
BSP proceeds to the next task without waiting for the AP. If a non-blocking mode
is requested after the UEFI Event EFI_EVENT_GROUP_READY_TO_BOOT is signaled,
then EFI_UNSUPPORTED must be returned.
@@ -636,7 +635,7 @@ Done:
EFI_EVENT is defined in CreateEvent() in
the Unified Extensible Firmware Interface
Specification.
-  @param[in]  TimeoutInMicrosecsond   Indicates the time limit in microseconds for
+  @param[in]  TimeoutInMicroseconds   Indicates the time limit in microseconds for
APs to return from Procedure, either for
blocking or non-blocking mode. Zero means
infinity.  If the timeout expires before
diff --git a/EmulatorPkg/EmuBlockIoDxe/EmuBlockIo.c b/EmulatorPkg/EmuBlockIoDxe/EmuBlockIo.c
index 96424a82ae..1a88223f91 100644
--- a/EmulatorPkg/EmuBlockIoDxe/EmuBlockIo.c
+++ b/EmulatorPkg/EmuBlockIoDxe/EmuBlockIo.c
@@ -13,7 +13,7 @@ bbe

@param[in]  This                 Indicates a pointer to the calling context.
@param[in]  ExtendedVerification Indicates that the driver may perform a more
-                                   exhausive verfication operation of the device
+                                   exhaustive verification operation of the device
during reset.

@retval EFI_SUCCESS          The device was reset.
@@ -123,7 +123,7 @@ EmuBlockIo2ReadBlocksEx (
the Event is NULL.
@retval EFI_WRITE_PROTECTED   The device can not be written to.
@retval EFI_NO_MEDIA          There is no media in the device.
-  @retval EFI_MEDIA_CHNAGED     The MediaId does not matched the current device.
+  @retval EFI_MEDIA_CHANGED     The MediaId does not match the current device.
@retval EFI_DEVICE_ERROR      The device reported an error while performing the write.
@retval EFI_BAD_BUFFER_SIZE   The Buffer was not a multiple of the block size of the device.
@retval EFI_INVALID_PARAMETER The write request contains LBAs that are not valid,
@@ -172,7 +172,7 @@ EmuBlockIo2WriteBlocksEx (
@retval EFI_SUCCESS          The flush request was queued if Event is not NULL.
All outstanding data was written correctly to the
device if the Event is NULL.
-  @retval EFI_DEVICE_ERROR     The device reported an error while writting back
+  @retval EFI_DEVICE_ERROR     The device reported an error while writing back
the data.
@retval EFI_WRITE_PROTECTED  The device cannot be written to.
@retval EFI_NO_MEDIA         There is no media in the device.
@@ -250,7 +250,7 @@ EmuBlockIoReset (
@retval EFI_SUCCESS           The data was read correctly from the device.
@retval EFI_DEVICE_ERROR      The device reported an error while performing the read.
@retval EFI_NO_MEDIA          There is no media in the device.
-  @retval EFI_MEDIA_CHANGED     The MediaId does not matched the current device.
+  @retval EFI_MEDIA_CHANGED     The MediaId does not match the current device.
@retval EFI_BAD_BUFFER_SIZE   The Buffer was not a multiple of the block size of the device.
@retval EFI_INVALID_PARAMETER The read request contains LBAs that are not valid,
or the buffer is not on proper alignment.
@@ -297,7 +297,7 @@ EmuBlockIoReadBlocks (
@retval EFI_WRITE_PROTECTED   The device can not be written to.
@retval EFI_DEVICE_ERROR      The device reported an error while performing the write.
@retval EFI_NO_MEDIA          There is no media in the device.
-  @retval EFI_MEDIA_CHNAGED     The MediaId does not matched the current device.
+  @retval EFI_MEDIA_CHANGED     The MediaId does not match the current device.
@retval EFI_BAD_BUFFER_SIZE   The Buffer was not a multiple of the block size of the device.
@retval EFI_INVALID_PARAMETER The write request contains LBAs that are not valid,
or the buffer is not on proper alignment.
@@ -335,7 +335,7 @@ EmuBlockIoWriteBlocks (
@param  This              Indicates a pointer to the calling context.

@retval EFI_SUCCESS       All outstanding data was written to the device
-  @retval EFI_DEVICE_ERROR  The device reported an error while writting back the data
+  @retval EFI_DEVICE_ERROR  The device reported an error while writing back the data
@retval EFI_NO_MEDIA      There is no media in the device.

**/
@@ -484,7 +484,7 @@ EmuBlockIoDriverBindingSupported (
@retval EFI_SUCCESS              The device was started.
@retval EFI_DEVICE_ERROR         The device could not be started due to a device error.Currently not implemented.
@retval EFI_OUT_OF_RESOURCES     The request could not be completed due to a lack of resources.
-  @retval Others                   The driver failded to start the device.
+  @retval Others                   The driver failed to start the device.

**/
EFI_STATUS
diff --git a/EmulatorPkg/EmuGopDxe/GopDriver.c b/EmulatorPkg/EmuGopDxe/GopDriver.c
index d0215c33e7..595c49a332 100644
--- a/EmulatorPkg/EmuGopDxe/GopDriver.c
+++ b/EmulatorPkg/EmuGopDxe/GopDriver.c
@@ -165,7 +165,7 @@ EmuGopDriverBindingSupported (
@retval EFI_SUCCESS              The device was started.
@retval EFI_DEVICE_ERROR         The device could not be started due to a device error.Currently not implemented.
@retval EFI_OUT_OF_RESOURCES     The request could not be completed due to a lack of resources.
-  @retval Others                   The driver failded to start the device.
+  @retval Others                   The driver failed to start the device.

**/
EFI_STATUS
@@ -196,7 +196,7 @@ EmuGopDriverBindingStart (
}

//
-  // Allocate Private context data for SGO inteface.
+  // Allocate Private context data for SGO interface.
//
Private = NULL;
Status = gBS->AllocatePool (
diff --git a/EmulatorPkg/EmuGopDxe/GopInput.c b/EmulatorPkg/EmuGopDxe/GopInput.c
index fdd0b49115..44502900c5 100644
--- a/EmulatorPkg/EmuGopDxe/GopInput.c
+++ b/EmulatorPkg/EmuGopDxe/GopInput.c
@@ -283,7 +283,7 @@ EmuGopSimpleTextInExResetEx (
/*++

Routine Description:
-    Reset the input device and optionaly run diagnostics
+    Reset the input device and optionally run diagnostics

Arguments:
This                 - Protocol instance pointer.
@@ -358,7 +358,7 @@ EmuGopSimpleTextInExReadKeyStrokeEx (

Routine Description:
Reads the next keystroke from the input device. The WaitForKey Event can
-    be used to test for existance of a keystroke via WaitForEvent () call.
+    be used to test for existence of a keystroke via WaitForEvent () call.

Arguments:
This       - Protocol instance pointer.
@@ -367,7 +367,7 @@ EmuGopSimpleTextInExReadKeyStrokeEx (

Returns:
EFI_SUCCESS           - The keystroke information was returned.
-    EFI_NOT_READY         - There was no keystroke data availiable.
+    EFI_NOT_READY         - There was no keystroke data available.
EFI_DEVICE_ERROR      - The keystroke information was not returned due to
hardware errors.
EFI_INVALID_PARAMETER - KeyData is NULL.
@@ -660,7 +660,7 @@ EmuGopSimpleTextInExUnregisterKeyNotify (

/**
-  Initialize SimplelTextIn and SimpleTextInEx protocols in the Private
+  Initialize SimpleTextIn and SimpleTextInEx protocols in the Private
context structure.

@param  Private               Context structure to fill in.
@@ -676,7 +676,7 @@ EmuGopInitializeSimpleTextInForWindow (
EFI_STATUS  Status;

//
-  // Initialize Simple Text In protoocol
+  // Initialize Simple Text In protocol
//
Private->SimpleTextIn.Reset         = EmuGopSimpleTextInReset;
Private->SimpleTextIn.ReadKeyStroke = EmuGopSimpleTextInReadKeyStroke;
@@ -879,7 +879,7 @@ EmuGopInitializeSimplePointerForWindow (
EFI_STATUS  Status;

//
-  // Initialize Simple Pointer protoocol
+  // Initialize Simple Pointer protocol
//
Private->PointerMode.ResolutionX = 1;
Private->PointerMode.ResolutionY = 1;
diff --git a/EmulatorPkg/EmuGopDxe/GopScreen.c b/EmulatorPkg/EmuGopDxe/GopScreen.c
index fbac649f8b..f1fee4d6c0 100644
--- a/EmulatorPkg/EmuGopDxe/GopScreen.c
+++ b/EmulatorPkg/EmuGopDxe/GopScreen.c
@@ -10,7 +10,7 @@ Module Name:

Abstract:

-  This file produces the graphics abstration of UGA. It is called by
+  This file produces the graphics abstraction of UGA. It is called by
EmuGopDriver.c file which deals with the EFI 1.1 driver model.
This file just does graphics.

@@ -172,12 +172,12 @@ EmuGopSetMode (
@param  DestinationX X coordinate of destination for the BltBuffer.
@param  DestinationY Y coordinate of destination for the BltBuffer.
@param  Width        Width of rectangle in BltBuffer in pixels.
-  @param  Height       Hight of rectangle in BltBuffer in pixels.
+  @param  Height       Height of rectangle in BltBuffer in pixels.
@param  Delta        OPTIONAL

@retval EFI_SUCCESS           The Blt operation completed.
@retval EFI_INVALID_PARAMETER BltOperation is not valid.
-  @retval EFI_DEVICE_ERROR      A hardware error occured writting to the video buffer.
+  @retval EFI_DEVICE_ERROR      A hardware error occurred writing to the video buffer.

**/
EFI_STATUS
diff --git a/EmulatorPkg/EmuThunkDxe/EmuThunk.c b/EmulatorPkg/EmuThunkDxe/EmuThunk.c
index d26d52ae36..ef791eedce 100644
--- a/EmulatorPkg/EmuThunkDxe/EmuThunk.c
+++ b/EmulatorPkg/EmuThunkDxe/EmuThunk.c
@@ -63,7 +63,7 @@ Arguments:
(Standard EFI Image entry - EFI_IMAGE_ENTRY_POINT)

Returns:
-  EFI_SUCEESS - UnixThunk protocol is added or error status from
+  EFI_SUCCESS - UnixThunk protocol is added or error status from
gBS->InstallMultiProtocolInterfaces().

**/
--
2.20.1 (Apple Git-117)

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#43175): https://edk2.groups.io/g/devel/message/43175
Mute This Topic: https://groups.io/mt/32288190/1813853
Group Owner: devel+owner at edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub  [edk2-devel-archive at redhat.com]
-=-=-=-=-=-=-=-=-=-=-=-

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/edk2-devel-archive/attachments/20190702/c2cf6cd8/attachment.htm>


More information about the edk2-devel-archive mailing list