summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* pip: update edk2-pytool-extensions requirementdependabot/pip/edk2-pytool-extensions-approx-eq-0.28.1dependabot[bot]2025-02-051-1/+1
| | | | | | | | | | | | | Updates the requirements on [edk2-pytool-extensions](https://github.com/tianocore/edk2-pytool-extensions) to permit the latest version. - [Release notes](https://github.com/tianocore/edk2-pytool-extensions/releases) - [Commits](https://github.com/tianocore/edk2-pytool-extensions/compare/v0.27.10...v0.28.1) --- updated-dependencies: - dependency-name: edk2-pytool-extensions dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
* ReadMe.rst: reflect bugzilla migrationLeif Lindholm2025-02-041-12/+3
| | | | | | | | | | | | | | | We've migrated bugzilla bugs to github issues, so update the references to specific bugs called out in the top-level readme. Also delete the references to BZ2661 and BZ2668 which are both *closed*: https://github.com/tianocore/edk2/issues/8453 https://github.com/tianocore/edk2/issues/8458 And drop bugzilla.tianocore.org from "references". The server is no longer in use, and the certificate has expired, so stop telling people to go there. Signed-off-by: Leif Lindholm <leif.lindholm@oss.qualcomm.com>
* License-History.txt: Reflect bugzilla migrationMichael Kubacki2025-02-041-4/+4
| | | | | | | Update BZ links to corresponding GitHub issues links now that the BZ -> GitHub issue migration is complete. Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
* SignedCapsulePkg: make Doxygen interpret ASCII art as verbatim textRebecca Cran2025-02-041-2/+4
| | | | | | | | | By default, Doxygen tries to nicely format all text within doc blocks. Unfortunately this mangles ASCII art: add @verbatim statements to EdkiiSystemFmpCapsule.h to cause Doxygen to display the text as provided. Signed-off-by: Rebecca Cran <rebecca@bsdio.com>
* BaseTools: Add @verbatim as allowed Doxygen tagRebecca Cran2025-02-042-2/+2
| | | | | | | Per the discussion in https://github.com/tianocore/edk2/pull/6476, update Ecc code to allow the @verbatim Doxygen tag. Signed-off-by: Rebecca Cran <rebecca@bsdio.com>
* UefiPayloadPkg: Revert 4KB alignment of CLANGDWARF buildChasel Chiu2025-02-031-1/+0
| | | | | | | | | With the latest GccBase.lds combining with CLANG build, there is no need to enforce 4KB alignment of in UPL CLANGDWARF build. This reverts commit b3bfb8f22d43bd9577df85bec20e75eb2f659990. Signed-off-by: Chasel Chiu <chasel.chiu@intel.com>
* BaseTools: Add /DRIVER to CLANGPDB link flagsDionna Glaze2025-02-031-6/+6
| | | | | | This quiets the warning reported in Issue #10637. Signed-off-by: Dionna Glaze <dionnaglaze@google.com>
* MdePkg/IndustryStandard: add definitions for CXL CEDTYuquan Wang2025-02-033-0/+147
| | | | | | | This adds #defines and struct typedefs for the various structure types in the CXL Early Discovery Table (CEDT). Signed-off-by: Yuquan Wang <wangyuquan1236@phytium.com.cn>
* BaseTools/AutoGen: GenMake response file quotes stringsMichael D Kinney2025-02-021-3/+14
| | | | | | | | | | | If command line options are moved into a response file of a GCC family build, then the file path separators are converted from '\' to '/'. However, this can corrupt command line options that are quoted strings. Update GenMake to no convert '\' to '/' in quoted strings. Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
* BaseTools/tools_def: Remove no-warn-rwx-segments linker optionsArd Biesheuvel2025-02-021-8/+3
| | | | | | | | | | | | | | The linker option 'no-warn-rwx-segments' breaks both the LLVM linker and versions of the binutils ld.bfd linker prior to 2.39. Now that the ELF image is made up of separate R-X and RW- segments, this warning is no longer emitted and so there is no longer a need to suppress it either. While at it, move GCC_DLINK_FLAGS_COMMON (which is not common but only used by Ia32 and X64) into its only user so it can be dropped. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* BaseTools/Scripts/GccBase.lds: Use separate R-W and RW- ELF segmentsArd Biesheuvel2025-02-021-3/+11
| | | | | | | | | | | | To prevent the ELF linkers from complaining about emitted ELF segments that require both writable and executable permissions, define two separate R-X and RW- ELF segments, and emit the output sections explicitly into those segments as appropriate. Note that this has no bearing on the PE image, and using a single RW- segment would probably be fine too. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* BaseTools/Scripts: Merge GCC and Clang ELF linker scriptsArd Biesheuvel2025-02-023-94/+4
| | | | | | | | | | | | | | The original reason for creating a separate version of the ELF linker script for Clang was the difference between COMMONPAGESIZE and MAXPAGESIZE, which can we provided on the command line to the respective linkers (ld.bfd versus lld). That difference no longer exists, and both use COMMONPAGE_SIZE. So there is no longer a need to maintain a fork, which has already been going out of sync with the original for no good reason. So merge the two and call it GccBase.lds Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* BaseTools/Scripts/ClangBase.lds: Move .entry into .text sectionArd Biesheuvel2025-02-021-4/+1
| | | | | | | | | | | | | | | | The GccBase.lds and ClangBase.lds ELF linker scripts have been laid out very carefully to ensure that the memory mappings of .text and .data are such that they can be preserved in the PE/COFF memory image. This removes the need to update any place-relative ELF relocations when generating the PE/COFF image, making its job much easier, and potentially allowing it to disregard static ELF relocations altogether, and rely solely on dynamic ELF relocations. Adding an arbitrary .entry section before .text breaks those assumptions, so instead of emitting it as a separate section, move its payload to the start of .text. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* UefiPayloadPkg: Update Elf segment/section syncup processChasel Chiu2025-02-021-13/+58
| | | | | | | | | | Original ELF segment/section syncup process having layout assumption which has caused build failure when layout changing. New process will parse both existing segments and sections firstly to support different layout. Signed-off-by: Chasel Chiu <chasel.chiu@intel.com>
* BaseTools/tools_def: Use no-warn-rwx-segments only for GCC5Ard Biesheuvel2025-02-011-3/+3
| | | | | | | | | | | | | The command line option --no-warn-rwx-segments was added to the linker command line for all GCC family builds on ARM and AARCH64, including CLANGDWARF and GCC49 and older, none of which are intended for use with linkers that actually understand this option. So instead, move it to the GCC5 DLINK FLAGS definitions for ARM and AARCH64 (which are inherited by the versionless GCC which is intended to replace GCC5 at some point). Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* MdePkg: Add Hot pluggable resource attributeINDIA\sachinganesh2025-01-311-1/+2
| | | | | | PI 1.9 Specification defines new memory resource attribute for hot plug. Signed-off-by: Sachin Ganesh <sachinganesh@ami.com>
* MdePkg: Add UEFI 2.11 specification macroINDIA\sachinganesh2025-01-311-0/+1
| | | | | | Add macro for UEFI 2.11 Specification support Signed-off-by: Sachin Ganesh <sachinganesh@ami.com>
* MdePkg: Add Confidential Computing Extension for RISC-V AP-TEEINDIA\sachinganesh2025-01-311-3/+4
| | | | | | | UEFI 2.11 Specification adds RISC-V AP-TEE Confidential Computing Extension Signed-off-by: Sachin Ganesh <sachinganesh@ami.com>
* MdePkg: Add HotPlug Memory AttributeINDIA\sachinganesh2025-01-311-0/+10
| | | | | | UEFI 2.11 Specification defines new memory attribute for hot plug. Signed-off-by: Sachin Ganesh <sachinganesh@ami.com>
* ArmPkg: Retire ArmDisassemblerLibArd Biesheuvel2025-01-317-1657/+0
| | | | | | No longer used anywhere so can be retired. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* Revert "ArmVirtPkg/ArmVirtQemu: Reduce MMIO region mapped by default"Gerd Hoffmann2025-01-311-7/+7
| | | | | | | | | This reverts commit 43233ff9f88e5c9b88228810f7725bade4cdfecf. The TPM code (and possibly others too) must be fixed to also map their MMIO ranges before we can do this cleanup. Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
* ArmVirtPkg: turn off debug logging for VirtioSerialDxeGerd Hoffmann2025-01-311-1/+4
| | | | | | | | | | When running the verbose builds on arm for development and testing it is quite convenient to use virtio serial to interact with the system because console and logging are separated then. Except that the virtio serial driver spams the debug log in that case. Set the debug level for the driver to zero to avoid that. Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
* Maintainers: update my email addressAndrei Warkentin2025-01-311-2/+2
| | | | | | I'm no longer at Intel. Signed-off-by: Andrei Warkentin <andyw@imsa.edu>
* BaseTools/Pccts: set C standardGerd Hoffmann2025-01-312-2/+2
| | | | | | | | The prehistoric code base doesn't build with ISO C23. Set the C standard to C11 (for both clang and gcc) so it continues to build with gcc 15 (which uses C23 by default). Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
* MdePkg/BaseFdtLib: fix build with gcc 15Gerd Hoffmann2025-01-311-9/+13
| | | | | | | | gcc 15 switched to use the new ISO C23 standard by default. 'bool', 'true' and 'false' are keywords in C23, so do not try to define them. Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
* MdePkg: Add SM3 crypto algorithm GUID definitionLiming Gao2025-01-312-0/+39
| | | | | | | UEFI 2.11 has been published on https://uefi.org/specifications It defines SM3 crypto algorithm GUID and structure. Signed-off-by: Liming Gao <gaoliming@byosoft.com.cn>
* Devcontainer: Use latest Fedora 40 imageOliver Steffen2025-01-311-1/+1
| | | | | | | Since the CI is now running on Fedora 40, let's also switch over VSCode Devcontainer to use the same. Signed-off-by: Oliver Steffen <osteffen@redhat.com>
* .github/codeql.yml: Drop ArmPkg IA32 and X64 from build matrixMichael Kubacki2025-01-301-2/+0
| | | | | | | These archs are not supported by ArmPkg so we can save agent resources by not attempting to schedule their CodeQL build. Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
* ArmVirtPkg: Drop reference to ArmDisassemblerLibArd Biesheuvel2025-01-301-1/+0
| | | | | | ArmDisassemblerLib is going away ... Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg: Stop using ArmDisassemblerLibArd Biesheuvel2025-01-305-35/+1
| | | | | | | | | | | | | | | | | | | | ArmDisassemblerLib is used to pretty print the instruction that triggered an unhandled exception, but it was never implemented for AARCH64, and according to the existing file comment, Thumb2 support (which is used predominantly when building EDK2 for 32-bit ARM due to its smaller size) is incomplete. The DEBUG diagnostics that are produced on an unhandled exception are generally sufficient to dump the entire executable that triggered it, and so this disassembly is of limited value, especially because it doesn't work on AARCH64. So let's start getting rid of it, by dropping references to it in code and in the various .INF and .DSC files. Once out-of-tree platforms have been allowed to catch up, we can remove the library implementation and its class definition entirely. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg,ArmPkg/ArmExceptionLib: drop vector relocation variant/supportLeif Lindholm2025-01-309-252/+21
| | | | | | | | | | | | There were several bugs in the vector table relocation code which means it can't really have been used by anyone on AArch64 in the last decade or so. So delete the support code from the library, as well as the ArmRelocateExceptionLib.inf file. This gets rid of PcdDebuggerExceptionSupport (including a duff reference in CpuDxe), PcdCpuVectorBaseAddress and PcdRelocateVectorTable. Signed-off-by: Leif Lindholm <leif.lindholm@oss.qualcomm.com>
* ArmVirtPkg/ArmVirtQemu: Reduce MMIO region mapped by defaultArd Biesheuvel2025-01-301-7/+7
| | | | | | | | | | | | Currently, the ArmVirtQemu startup code maps a 128 MiB of MMIO space, as it knows that the UART, GIC and RTC live there. Now that the GIC driver maps its MMIO registers itself, there is no need for this region to cover its MMIO space. And there are other regions here that don't need to be mapped by default: the only ones that need to be mapped are the UARTS, the RTC, the fw_cfg MMIO interface and the virtio-mmio regions, all of which live in a 32 MiB window starting at address 0x900_0000. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg/ArmGicDxe: Map GIC MMIO regions before useArd Biesheuvel2025-01-303-11/+62
| | | | | | | | | | | | | | | The GIC driver itself has intimate knowledge of the hardware, and so it is the best suited to create the mappings of the MMIO control regions, in case they have not been mapped yet by the platform code. So call in the the CPU arch protocol to map the CPU interface, distributor and redistributor regions as they are discovered by the GIC driver startup code. Note that creating these mappings has no effect if the regions in question have already been mapped with the correct attributes. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg/ArmGicDxe: Remove pointless passing around of MMIO addressesArd Biesheuvel2025-01-301-29/+12
| | | | | | | | The GIC distributor and redistributor addresses that are passed into the interrupt enable and disable routines are always the same, so just use the global variables directly. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg/ArmGicDxe: Avoid pointless repeated iteration over GIC framesArd Biesheuvel2025-01-301-46/+13
| | | | | | | | | The GIC DXE driver only runs on the boot CPU, and so there is really no point in iterating over all the redistributor frames every time an interrupt is enabled, disabled or its state tested. Instead, do this only at load time. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg/ArmGicDxe: Replace CpuArch registration event with DEPEXArd Biesheuvel2025-01-305-66/+20
| | | | | | | | | | | | Instead of relying on a protocol notification event to register the core IRQ interrupt handler with CPU arch protocol once it becomes available, use a DEPEX to ensure that the GIC driver is not dispatched at all until the CPU arch protocol has turned up. This will allow the GIC driver to use other CPU arch protocol methods, such as the ones needed to map the GIC MMIO regions at driver startup. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg/CpuDxe: Replace DEPEX on h/w protocol with event notificationArd Biesheuvel2025-01-302-4/+106
| | | | | | | | | | | | | | | | | | | | | | | | | Currently, ArmPkg's CpuDxe DEPEXes on the hardware interrupt protocol, to ensure that it is not dispatched before the GIC driver. This way, the CpuDxe driver is guaranteed not to enable interrupts on the CPU side before the GIC driver has had the opportunity to configure the interrupts on the distribution side. However, this prevents the GIC driver from using any of the CPU arch protocol interfaces, such as mapping memory, which it may need to do on platforms where the GIC MMIO regions are not mapped yet when the driver is started. So instead, use a protocol notification on the hardware interrupt protocol, which is installed by the GIC driver (as well as other existing interrupt controller drivers for platforms that do not implement a GIC) after it starts up and deasserts and disables all incoming interrupts. Manipulate the interrupt state as usual only after this notification has been received. Before that, keep track of the caller's intent regarding the interrupt enabled state in a shadow variable, but do not actually enable interrupt delivery to the CPU just yet. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg/CpuDxe: Remove rudimentary vector handoff logicArd Biesheuvel2025-01-303-43/+5
| | | | | | | | | | | | | | | | There is some fossilized code in the CpuDxe driver startup code that permits a vector table to be inherited from the PEI stage, but this code is essentially dead on ARM platforms, given that the VectorInfo argument passed to InitializeCpuExceptionHandlers() is ignored, and no code appears to exist that would result in the gEfiVectorHandoffTableGuid configuration table ever being populated. Also, due to prior refactoring, the code that disables and re-enables IRQs and FIQs is completely pointless, and can simply be removed. That, in turn, allows the CPU arch protocol parameter to be dropped from the prototype of InitializeExceptions(). Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg/CpuDxe: Use STATIC linkage where possibleArd Biesheuvel2025-01-302-1/+10
| | | | | | | | Use static linkage for variables and routines that are not referenced from other objects. This is generally preferred, because it gives the compiler more freedom for optimization. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ArmPkg/CpuDxe: Fix error handling in driver initializationArd Biesheuvel2025-01-301-4/+10
| | | | | | | | | | | | | | | | | | | Failure to install the CPU arch protocol is a fatal error, so treat it as such, rather than ignore it, even though we won't get very far if this driver fails to dispatch - at least, we will get an error in a DEBUG build rather than a mysterious failure due to unsatisfied DEPEXes. Failure to install the idle loop event handler is not a fatal error, and it should not cause the driver to exit with an error, as this will unload the driver and keep the installed CPU arch protocol pointer dangling. So keep the ASSERT() on the return value, but return EFI_SUCCESS once we're past the point where the CPU arch protocol has been installed. Since the protocol is never uninstalled, make the CPU handle function local, as there is no point in keeping its value around. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* Maintainers.txt: Update EmulatorPkg maintainersMichael Kubacki2025-01-291-0/+2
| | | | | | Add Oliver Smith-Denny and Michael Kubacki as maintainers. Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
* UnitTestFrameworkPkg: Fix false positives from address sanitizerMichael D Kinney2025-01-291-23/+23
| | | | | | | | | | | | | | | | | | | | | | PR #6408 introduced a host specific NORETURN function to resolve false positives from the address sanitizer when LongJump() is called and the stack is reset to a previous stack frame. This approach was discussed here: https://github.com/tianocore/edk2/pull/6408/files#r1918810499 False positives are still being observed with this initial solution. The address sanitizer provides __asan_handle_no_return() to clean up shadow memory before a NORETURN function is called and provides a simpler implementation for this issue without having to introduce a host specific NORETURN function. https://github.com/llvm/llvm-project/blob/main/compiler-rt/include/sanitizer/asan_interface.h Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
* MdePkg/BasePeCoffLib: Remove DEBUG() statements from runtime codeArd Biesheuvel2025-01-291-2/+6
| | | | | | | | | | | | | PeCoffLoaderRelocateImageForRuntime() executes after boot services, and so it should not use DEBUG() prints at all, given that these may rely on MMIO mappings or other boot time facilities that are no longer available. So revert the changes in aedcaa3df8a2 ("MdePkg: Fix overflow issue in PeCoffLoaderRelocateImageForRuntime") that replaced code comments with DBEUG() statements. Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
* ShellPkg: fix warnings about uninitialized variableMike Maslenkin2025-01-291-10/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Dmem.c: In function 'GetImageExecutionInfo': Dmem.c:241:10: error: 'Status' may be used uninitialized in this function [-Werror=maybe-uninitialized] return Status; ^~~~~~ Dmem.c:284:35: note: 'Status' was declared here EFI_STATUS Status; ^~~~~~ Dmem.c: In function 'ShellCommandRunDmem': Dmem.c:586:27: error: 'ConformanceProfileTableAddress' may be used uninitialized in this function [-Werror=maybe-uninitialized] ShellStatus = DisplayConformanceProfiles (ConformanceProfileTableAddress); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dmem.c:582:27: error: 'ImageExecutionTableAddress' may be used uninitialized in this function [-Werror=maybe-uninitialized] ShellStatus = DisplayImageExecutionEntries (ImageExecutionTableAddress); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dmem.c:578:27: error: 'RtPropertiesTableAddress' may be used uninitialized in this function [-Werror=maybe-uninitialized] ShellStatus = DisplayRtProperties (RtPropertiesTableAddress); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
* OvmfPkg: fix warning about uninitialized variableMike Maslenkin2025-01-291-0/+1
| | | | | | | | | | | | | | | | | | | | | | | GenericQemuLoadImageLib.c: In function 'QemuLoadKernelImage': GenericQemuLoadImageLib.c:323:5: error: 'CommandLine' may be used uninitialized in this function [-Werror=maybe-uninitialized] UnicodeSPrintAsciiFormat ( ^~~~~~~~~~~~~~~~~~~~~~~~~~ KernelLoadedImage->LoadOptions, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ KernelLoadedImage->LoadOptionsSize, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "%a%a", ~~~~~~~ (CommandLineSize == 0) ? "" : CommandLine, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (InitrdSize == 0) ? "" : " initrd=initrd" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ); ~ cc1: all warnings being treated as errors Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
* SecurityPkg/RngDxe: fix warning about uninitialized variableMike Maslenkin2025-01-291-1/+5
| | | | | | | | | | | | ArmTrng.c: In function 'GenerateEntropy': ArmTrng.c:40:15: error: 'Status' may be used uninitialized in this function [-Werror=maybe-uninitialized] EFI_STATUS Status; ^~~~~~ cc1: all warnings being treated as errors Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
* MdeModulePkg: NvmExpressDxe: fix warning about uninitialized variableMike Maslenkin2025-01-291-0/+2
| | | | | | | | | | | | NvmExpressMediaSanitize.c: In function 'NvmExpressMediaClear': NvmExpressMediaSanitize.c:337:29: error: 'Status' may be used uninitialized in this function [-Werror=maybe-uninitialized] EFI_STATUS Status; ^~~~~~ cc1: all warnings being treated as errors Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
* MdeModulePkg: fix warning about uninitialized variableMike Maslenkin2025-01-291-0/+2
| | | | | | | | | | | Handle.c:1302:24: error: 'Prot' may be used uninitialized in this function [-Werror=maybe-uninitialized] *Interface = Prot->Interface; ~~~~^~~~~~~~~~~ cc1: all warnings being treated as errors Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
* MdeModulePkg: PeiMain: fix warning about uninitialized variableMike Maslenkin2025-01-291-5/+5
| | | | | | | | | | Dispatcher.c:1639:34: error: 'FvMigrationFlags' may be used uninitialized in this function [-Werror=maybe-uninitialized] (((FvMigrationFlags & FLAGS_FV_MIGRATE_BEFORE_PEI_CORE_REENTRY) == 0) || ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
* OvmfPkg/QemuKernelLoaderFsDxe: use SIZE_OF_EFI_FILE_INFOGerd Hoffmann2025-01-281-1/+1
| | | | Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
generated by cgit (git 2.34.1) at 2025-02-22 16:46:04 +0000