summaryrefslogtreecommitdiffstats
path: root/OvmfPkg/Library/QemuBootOrderLib
diff options
context:
space:
mode:
authorAntoine Coeur <coeur@gmx.fr>2020-02-07 02:08:10 +0100
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>2020-02-10 22:30:07 +0000
commita2e75595766b370bf12207b716f9fbf1b5895445 (patch)
tree7f20f233f8e11e33bde3f1e1be7383d77b2b94af /OvmfPkg/Library/QemuBootOrderLib
parentf6fc95c943c1907ac44404c4937937febf13fe80 (diff)
downloadedk2-a2e75595766b370bf12207b716f9fbf1b5895445.tar.gz
edk2-a2e75595766b370bf12207b716f9fbf1b5895445.tar.bz2
edk2-a2e75595766b370bf12207b716f9fbf1b5895445.zip
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>
Diffstat (limited to 'OvmfPkg/Library/QemuBootOrderLib')
-rw-r--r--OvmfPkg/Library/QemuBootOrderLib/QemuBootOrderLib.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/OvmfPkg/Library/QemuBootOrderLib/QemuBootOrderLib.c b/OvmfPkg/Library/QemuBootOrderLib/QemuBootOrderLib.c
index 586c2dec12..ceffb17fa6 100644
--- a/OvmfPkg/Library/QemuBootOrderLib/QemuBootOrderLib.c
+++ b/OvmfPkg/Library/QemuBootOrderLib/QemuBootOrderLib.c
@@ -412,7 +412,7 @@ typedef struct {
If the call doesn't succeed, the contents of this
structure is indeterminate.
- @param[out] IsFinal In case of successul parsing, this parameter signals
+ @param[out] IsFinal In case of successful parsing, this parameter signals
whether the node just parsed is the final node in the
device path. The call after a final node will attempt
to start parsing the next path. If the call doesn't