summaryrefslogtreecommitdiffstats
path: root/CorebootModulePkg
diff options
context:
space:
mode:
authorLaszlo Ersek <lersek@redhat.com>2017-02-21 13:56:48 +0100
committerLaszlo Ersek <lersek@redhat.com>2017-02-22 03:35:37 +0100
commit6025488da39314d21e2a075b6ecc8d26d36b37e7 (patch)
tree129eb372321dfaad754e917a80a14a414bb3f60e /CorebootModulePkg
parenta3be3b65977eec894cebddf7100429aa0e84b669 (diff)
downloadedk2-6025488da39314d21e2a075b6ecc8d26d36b37e7.tar.gz
edk2-6025488da39314d21e2a075b6ecc8d26d36b37e7.tar.bz2
edk2-6025488da39314d21e2a075b6ecc8d26d36b37e7.zip
OvmfPkg/AcpiPlatformDxe: update PointerValue comments in "BootScript.c"
Commit df73df138d9d ("OvmfPkg/AcpiPlatformDxe: replay QEMU_LOADER_WRITE_POINTER commands at S3", 2017-02-09) added "BootScript.c" with such comments on the PointerValue field of CONDENSED_WRITE_POINTER, and on the corresponding PointerValue parameter of SaveCondensedWritePointerToS3Context(), that did not consider the then-latest update of the QEMU_LOADER_WRITE_POINTER structure. (Namely, the introduction of the PointeeOffset field.) The code is fine as-is -- ProcessCmdWritePointer() already calls SaveCondensedWritePointerToS3Context() correctly, and "BootScript.c" itself is indifferent to the exact values --, but the comments in "BootScript.c" should match reality too. Update them. Cc: Jordan Justen <jordan.l.justen@intel.com> Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Laszlo Ersek <lersek@redhat.com> Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
Diffstat (limited to 'CorebootModulePkg')
0 files changed, 0 insertions, 0 deletions