With the "Change-Id" line removed: Reviewed-by: Laszlo Ersek <lersek@...> Thanks Laszlo

(1) None of the patches should contain such a "Change-Id" line; they are meaningless for upstream edk2. They can be removed by the maintainer just before merging, of course. (2) However, I still

I'd like to regression-test this with OVMF and ArmVirtQemu, but I need a bit more time -- I just returned to work, and my email backlog is crushing. Thanks for your patience. Laszlo

Sorry for not reacting to this v2 series, I've been away. (I hope that my automated out-of-office response worked and let you know.) I'm glad that the patches are now merged. Thanks Laszlo

SBSA generic watchdog timer structure entry has been added to GTDT table as per SBSAv6.0. This enables acpi detection of wdt in qemu sbsa platform Cc: Leif Lindholm <leif@...> Cc: Ard

To enable detection of qemu SBSA generic watchdog timer device,this patch has been added to create sbsa-wdt entry into the GTDT table which helps firmware report the presence of SBSA-wdt to the

I've got this queued for review. I'll need some time for getting to it, as I've just returned after some absence, and everything seems to have collapsed on my head (as usual). Laszlo

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3D2594 This patch adds PCD PcdStatusCodeVariableIntegrity used to report the result of variable integrity check to platform, which should

Indeed, modifying just "Network.dsc.inc" is insufficient. "Network.dsc.inc" is convenient when it is applicable, but for some platforms, it is not flexible enough. That's why we have the separate DSC

Understood -- the build tool would not consider the user-originated prefix. The build tool would decide that the command is safe to start without using a response file, but the prefix would break

Since the limit is so small, there is no point in checking it against total amount of memory. For the time being, we should be fine with the limit you have suggested :)

- I don't have anything against this, as long as existent platforms are not required to adopt the new scheme. - The above description helps, but it is *still* too generic for me to understand: (a)

This version seems has reverteed to v1 re-indenting the whole file? Please base update on v2 where you did not do this. Thanks Graeme

Hi Abner, Comments inline. Thanks, Maciej I only meant that it would be reasonable to come up with a chunk-transfer limit that is dictated solely by Redfish use case, since it is currently the only

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3D3022=0D =0D The storage device erase behavior may have two possibilities:=0D 1.Write all data into "0"=0D 2.Write all data into "1"=0D but now

Now, in our SCT test case "CheckImage" behavior have some problems.Once=0D tool need to check the "EFI_SECURITY_VIOLATION" have correct return from=0D "EFI_FIRMWARE_MANAGEMENT_PROTOCOL->CheckImage"

Liming, Yes, it's also for other source files for AcpiTable, like *.asl. Thanks, Bob

Reviewed-by: Bob Feng <bob.c.feng@...>

Got it. Thanks. Nickle