OvmfPkg/Qemu: Fix various typos

Fix various typos in comments and documentation.

When "VbeShim.asm" is modified, we have to re-run "VbeShim.sh"
to update "VbeShim.h".
The string modified by this patch is only used when the DEBUG
macro (at the top of the file) is commented out. Since the
string is not referenced, NASM eliminates it, resulting in
the same byte array content in "VbeShim.h".

Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Antoine Coeur <coeur@gmx.fr>
Reviewed-by: Philippe Mathieu-Daude <philmd@redhat.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Signed-off-by: Philippe Mathieu-Daude <philmd@redhat.com>
Message-Id: <20200207010831.9046-58-philmd@redhat.com>
This commit is contained in:
Antoine Coeur
2020-02-07 02:08:10 +01:00
committed by mergify[bot]
parent f6fc95c943
commit a2e7559576
11 changed files with 25 additions and 25 deletions

View File

@@ -15,7 +15,7 @@
**/
//
// The protocols, PPI and GUID defintions for this module
// The protocols, PPI and GUID definitions for this module
//
#include <Protocol/DevicePath.h>
#include <Protocol/FirmwareVolumeBlock.h>
@@ -118,7 +118,7 @@ GetFvbInstance (
returned
Global - Pointer to ESAL_FWB_GLOBAL that contains all
instance data
FwhInstance - The EFI_FW_VOL_INSTANCE fimrware instance structure
FwhInstance - The EFI_FW_VOL_INSTANCE firmware instance structure
Returns:
EFI_SUCCESS - Successfully returns
@@ -695,7 +695,7 @@ FvbProtocolWrite (
Writes data beginning at Lba:Offset from FV. The write terminates either
when *NumBytes of data have been written, or when a block boundary is
reached. *NumBytes is updated to reflect the actual number of bytes
written. The write opertion does not include erase. This routine will
written. The write operation does not include erase. This routine will
attempt to write only the specified bytes. If the writes do not stick,
it will return an error.
@@ -740,7 +740,7 @@ FvbProtocolRead (
Reads data beginning at Lba:Offset from FV. The Read terminates either
when *NumBytes of data have been read, or when a block boundary is
reached. *NumBytes is updated to reflect the actual number of bytes
written. The write opertion does not include erase. This routine will
written. The write operation does not include erase. This routine will
attempt to write only the specified bytes. If the writes do not stick,
it will return an error.