From: Michael Kubacki <michael.kubacki@...> CheckTheImage() is currently used to provide the CheckImage() implementation for the EFI_FIRMWARE_MANAGEMENT_PROTOCOL instance produced by FmpDxe

From: Michael Kubacki <michael.kubacki@...> Introduces a public and a private header file to define more granular usage of the UEFI Specification defined unsuccessful vendor range for Last

From: Michael Kubacki <michael.kubacki@...> Adds the following macros to define the unsuccessful vendor range min and max (defined in UEFI Specification 2.8): 1.

From: Michael Kubacki <michael.kubacki@...> REF:https://bugzilla.tianocore.org/show_bug.cgi?id=2802 This patch series adds more granularity to Last Attempt Status codes reported during FMP

From: Michael Kubacki <michael.kubacki@...> The function ArmReplaceLiveTranslationEntry () is passed as a VOID pointer to WriteBackDataCacheRange (). This produces the following warning on

From: Michael Kubacki <michael.kubacki@...> REF:https://bugzilla.tianocore.org/show_bug.cgi?id=2835 There's several occurrences of a UINT64 or an EFI_PHYSICAL_ADDRESS being assigned to a

... I guess we might as well break the process for a noble purpose, every once in a while, so I went ahead and merged this... with just my R-b. - [lersek@...: supply missing space character

From: Michael Kubacki <michael.kubacki@...> The function ArmReplaceLiveTranslationEntry () is passed as a VOID pointer to WriteBackDataCacheRange (). This produces the following warning on

Reviewed-by: Laszlo Ersek <lersek@...>

Reviewed-by: Laszlo Ersek <lersek@...>

let's make that a Reviewed-by: Laszlo Ersek <lersek@...>

Reviewed-by: Laszlo Ersek <lersek@...>

s/vald/valid/ with that: Reviewed-by: Laszlo Ersek <lersek@...> Thanks laszlo

Yes, this is correct. Even though the Cpl offset is not on an 8 byte boundary and its size is not a full 8 bytes, any change in that qword range needs to be marked. The calculation will result in a

s/vald/valid/, twice With that fixed: Reviewed-by: Laszlo Ersek <lersek@...> Thanks Laszlo

I disagree. We should do whatever we can for avoiding cross-package patches, but in some cases, they are unavoidable. This is one of those cases. When reviewing v1, I immediately thought of doing

Laszlo, Yes. As a quick implementation, I am converting the source branch name to a directory name below gh-pages to store the draft and multiple releases in the single gh-pages branch. I could add

Hi Tom, I didn't notice this before, and from your response to Liming, I think you may have missed Liming pointing it out as well. Thanks Laszlo

(1) (same as earlier) please check for success before assigning the pointer (2) (same as earlier) style: please break off the closing paren, or condense all the arguments. Looks OK other than

(3) Style: for both gBS->AllocatePool() calls added in this patch, please either break the closing paren to a new line, or use the "condensed" style (which you do use elsewhere in these