tyler.durden
/
audk
mirror of https://github.com/acidanthera/audk.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

OvmfPkg: Fix typing errors 

Correct some typos (discovered with the codespell utility)

Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Thomas Huth <thuth@redhat.com>
Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
This commit is contained in:
Thomas Huth 2016-09-09 22:32:15 +02:00 committed by Laszlo Ersek
parent 3e92a99747
commit 8c0b0b34f7
9 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
OvmfPkg/AcpiPlatformDxe/QemuFwCfgAcpi.c
View File

@ -363,7 +363,7 @@ ProcessCmdAddChecksum (
array is an ACPI table, and if so, install it.
This function assumes that the entire QEMU linker/loader command file has
been processed successfuly in a prior first pass.
been processed successfully in a prior first pass.
@param[in] AddPointer The QEMU_LOADER_ADD_POINTER command to process.

4
OvmfPkg/Csm/CsmSupportLib/LegacyPlatform.c
View File

@ -256,8 +256,8 @@ GetSelectedVgaDeviceInfo (
*VgaHandle = NULL;
//
// Initialize variable states. Ths is important for selecting the VGA device
// if multiple devices exist behind a single bridge.
// Initialize variable states. This is important for selecting the VGA
// device if multiple devices exist behind a single bridge.
//
HandleCount = 0;
HandleBuffer = NULL;

4
OvmfPkg/Library/NvVarsFileLib/FsAccess.c
View File

@ -184,7 +184,7 @@ FileHandleEmpty (
@param[in] ReadSize - The size of data to read from the file
@return Pointer to buffer allocated to hold the file
contents. NULL if an error occured.
contents. NULL if an error occurred.
**/
VOID*
@ -332,7 +332,7 @@ LoadNvVarsFromFs (
// We write a variable to indicate we've already loaded the
// variable data. If it is found, we skip the loading.
//
// This is relevent if the non-volatile variable have been
// This is relevant if the non-volatile variable have been
// able to survive a reboot operation. In that case, we don't
// want to re-load the file as it would overwrite newer changes
// made to the variables.

8
OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c
View File

@ -1255,8 +1255,8 @@ ConnectRecursivelyIfPciMassStorage (
This notification function is invoked when the
EMU Variable FVB has been changed.
@param Event The event that occured
@param Context For EFI compatiblity. Not used.
@param Event The event that occurred
@param Context For EFI compatibility. Not used.
**/
VOID
@ -1480,8 +1480,8 @@ Routine Description:
This notification function is invoked when an instance of the
EFI_DEVICE_PATH_PROTOCOL is produced.
@param Event The event that occured
@param Context For EFI compatiblity. Not used.
@param Event The event that occurred
@param Context For EFI compatibility. Not used.
**/
VOID

2
OvmfPkg/PlatformPei/MemDetect.c
View File

@ -433,7 +433,7 @@ QemuInitializeRam (
// PEI RAM, in a backup buffer allocated with the normal PEI services.
// CpuMpPei restores the original contents ("returns" the borrowed area) at
// End-of-PEI. End-of-PEI in turn is emitted by S3Resume2Pei before
// transfering control to the OS's wakeup vector in the FACS.
// transferring control to the OS's wakeup vector in the FACS.
//
// We expect any other PEIMs that "borrow" memory similarly to CpuMpPei to
// restore the original contents. Furthermore, we expect all such PEIMs

2
OvmfPkg/QemuVideoDxe/VbeShim.c
View File

@ -134,7 +134,7 @@ InstallVbeShim (
PciWrite8 (Pam1Address, Pam1 | (BIT1 | BIT0));
//
// We never added memory space durig PEI or DXE for the C segment, so we
// We never added memory space during PEI or DXE for the C segment, so we
// don't need to (and can't) allocate from there. Also, guest operating
// systems will see a hole in the UEFI memory map there.
//

2
OvmfPkg/XenBusDxe/EventChannel.c
View File

@ -1,7 +1,7 @@
/** @file
Event Channel function implementation.
Event channel are use to notify of an event that happend in a shared
Event channel are use to notify of an event that happened in a shared
structure for example.
Copyright (C) 2014, Citrix Ltd.

2
OvmfPkg/XenBusDxe/XenStore.c
View File

@ -10,7 +10,7 @@
The XenStore is ASCII string based, and has a structure and semantics
similar to a filesystem. There are files and directories, the directories
able to contain files or other directories. The depth of the hierachy
able to contain files or other directories. The depth of the hierarchy
is only limited by the XenStore's maximum path length.
The communication channel between the XenStore service and other

2
OvmfPkg/XenPvBlkDxe/BlockIo.c
View File

@ -156,7 +156,7 @@ XenPvBlkDxeBlockIoReadWriteBlocks (
Sector += IoData.Size / 512;
Status = XenPvBlockIo (&IoData, IsWrite);
if (EFI_ERROR (Status)) {
DEBUG ((EFI_D_ERROR, "XenPvBlkDxe: Error durring %a operation.\n",
DEBUG ((EFI_D_ERROR, "XenPvBlkDxe: Error during %a operation.\n",
IsWrite ? "write" : "read"));
return Status;
}