Updates the library class to the name used for the header file
in the DEC file and used in consuming code.
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Remove library class warning messages and consistently link reset
logic across phases.
- Set all `HwResetSystemLib` instances to QEMU platform-specific
reset logic.
- Set Standalone MM driver and core `HwResetSystemLib` instances
to `BaseResetSystemLib.inf` in `QemuQ35Pkg`.
- QemuQ35Pkg:
- Add `HwResetSystemLib` library class to `BaseResetSystemLib`
and `DxeResetSystemLib` library instances.
- Drop phase bindings in `BaseResetSystemLib` as content is not
specific to those phases.
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
## Description
- Adds the BIOS version and date to Type 0 (BIOS) structure.
- Changes BIOS vendor to "Project Mu" so its easier to trace project
info.
- Adds the QEMU version to the Type 1 (System) version field.
- Q35: Changes System product from "MuQemuQ35" to "QEMU Q35".
- SBSA: Changes System product from "MuQemuQ35" to "QEMU SBSA".
- SBSA: Fixes asset tag values from "Q35" to "SBSA"
Other related minor cleanup.
The goal is to clean up firmware and system information and make it more
useful.
- [ ] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
on an a separate Web page, ...
## How This Was Tested
1. Verified values in QEMU run command.
2. Read values from `smbiosview` in the EFI shell.
3. Read relevant values from Windows UI.
## Integration Instructions
Review values modified and see if they affect tests or features
dependent on SMBIOS information.
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
## Description
`usb-tablet` and `usb-mouse` both override the default PS/2 emulation
when enabled. `usb-tablet` uses absolute coordinates and allows QEMU
to report the mouse position without grabbing the device.
It also tracks the mouse cursor more accurately.
- [ ] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
on an a separate Web page, ...
## How This Was Tested
QEMU Windows guest on Windows and Linux host.
## Integration Instructions
N/A
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
## Description
Fixes issue related to enabling TPM for QEMU Q35.
- [x] Impacts functionality?
- [ ] Impacts security?
- [ ] Breaking change?
- [ ] Includes tests?
- [ ] Includes documentation?
## How This Was Tested
Locally tested with Windows boot.
## Integration Instructions
N/A
Bumps Features/MM_SUPV from `8.1.1` to `8.1.2`
Introduces 1 new commit in
[Features/MM_SUPV](https://github.com/microsoft/mu_feature_mm_supv.git).
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps Common/MU from `2023020001.0.0` to `2023020001.0.1`
Introduces 5 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps Common/MU_OEM_SAMPLE from `2023020000.0.3` to `2023020000.0.4`
Introduces 7 new commits in
[Common/MU_OEM_SAMPLE](https://github.com/microsoft/mu_oem_sample.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
# Preface
Please ensure you have read the [contribution
docs](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md) prior
to submitting the pull request. In particular,
[pull request
guidelines](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md#pull-request-best-practices).
## Description
This adds support for both VHD and QCOW2 images by using the extension
to determine which storage rule should be used for qemu See [Issue
607](https://github.com/microsoft/mu_tiano_platforms/issues/607)
For each item, place an "x" in between `[` and `]` if true. Example:
`[x]`.
_(you can also check items in the GitHub UI)_
- [X] Impacts functionality?
- Adds back functionality for qcow2 images
- [ ] Impacts security?
- N/A
- [ ] Breaking change?
- N/A
- [ ] Includes tests?
- N/A
- [ ] Includes documentation?
- N/A
## How This Was Tested
This was used to run both a vhd image and a cow2 image, to confirm
backward compatibility the resultant string was also compared
## Integration Instructions
N/A
## Description
Commit 5a01f4f updated the YAML file to use the Ubuntu container
but did not replace DNF with APT when installing OpenSSL.
This change allows the release pipeline to work when using the
Ubuntu container.
- [ ] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
on an a separate Web page, ...
## How This Was Tested
Release pipeline.
## Integration Instructions
N/A
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps MU_BASECORE from `2023020002.1.1` to `2023020002.1.2`
Introduces 3 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
Removes "TARGET_ARCH" and "ACTIVE_PLATFORM" from being set inside the
RetrieveCommandLineOptions() function. These are already set in the
SetPlatformEnv() function, which is the common place for them to be set.
- [ ] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
on an a separate Web page, ...
## How This Was Tested
CI
## Integration Instructions
N/A
## Description
Adds a PrEval entry into the ci.yaml file, used for PrEval to evaluate
the newly added policy 5.
- [ ] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
on an a separate Web page, ...
## How This Was Tested
No tests necessary
## Integration Instructions
N/A
## Description
Changed the openssl inf version used to be the full version to match
expected functionality. Additionally disabled NETWORK_ISCSI_ENABLE as we
weren't using it.
Extra crypto functionality include:
1. Every SHA hash function. The default openssl version support SHA256
only.
2. X509 full functionality (this is connected with item 3)
3. ECC for TLS and other crypto features (item #2)
- [x] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [x] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
on an a separate Web page, ...
## How This Was Tested
Passed BaseCryptLib Unit Tests.
## Integration Instructions
N/A
Bumps MU_BASECORE from `2023020002.1.0` to `2023020002.1.1`
Introduces 2 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
# Preface
Please ensure you have read the [contribution
docs](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md) prior
to submitting the pull request. In particular,
[pull request
guidelines](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md#pull-request-best-practices).
## Description
Current SBSA is using timer based RngLib, which is not appropriate as an
example. This change updated the library to be instruction based.
Note that this instruction may not be available on all instructions
sets.
The change also updates to the latest TFA release for our own
housekeeping.
Fixes https://github.com/microsoft/mu_tiano_platforms/issues/616.
For each item, place an "x" in between `[` and `]` if true. Example:
`[x]`.
_(you can also check items in the GitHub UI)_
- [ ] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [x] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
on an a separate Web page, ...
## How This Was Tested
Booted SBSA platform firmware to Windows desktop.
## Integration Instructions
N/A
## Description
Remove unnecessary exemptions and extend lingering exemptions two weeks.
- [x] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
on an a separate Web page, ...
## How This Was Tested
CI pipelines
## Integration Instructions
N/A
Co-authored-by: Taylor Beebe <t@taylorbeebe.com>
Bumps Silicon/Arm/MU_TIANO from `2023020000.0.2` to `2023020000.0.3`
Introduces 1 new commit in
[Silicon/Arm/MU_TIANO](https://github.com/microsoft/mu_silicon_arm_tiano.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps Common/MU from `2023020000.1.0` to `2023020001.0.0`
Introduces 1 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
<details>
<summary>Commits</summary>
<ul>
<li><a
href="819d93ca1d">819d93</a>
AdvLoggerPkg: fix AdvLoggerSerialPortLib class (<a
href="https://github.com/microsoft/mu_plus/pull/268">#268</a>)</li>
</ul>
</details>
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
# Preface
Please ensure you have read the [contribution
docs](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md) prior
to submitting the pull request. In particular,
[pull request
guidelines](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md#pull-request-best-practices).
## Description
This change removed the individual policy initializers from platform
level since they are centralized to `ConfigKnobs`.
This change also removed the Depex in `ConfigKnobs` driver to fix the
dependency change.
Fixes https://github.com/microsoft/mu_tiano_platforms/issues/610.
For each item, place an "x" in between `[` and `]` if true. Example:
`[x]`.
_(you can also check items in the GitHub UI)_
- [x] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
on an a separate Web page, ...
## How This Was Tested
This change was tested on QemuSbsa and booted to Windows. The QemuQ35 is
also tested and booted to shell.
## Integration Instructions
N/A
Bumps MU_BASECORE from `2023020002.0.1` to `2023020002.0.4`
Introduces 18 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.git).
<details>
<summary>Commits</summary>
<ul>
<li><a
href="af60048223">af6004</a>
Refactoring the MM implementation to support both Standalone MM and
Traditional MM (<a
href="https://github.com/microsoft/mu_basecore/pull/461">#461</a>)</li>
<li><a
href="f784ee9063">f784ee</a>
Using older Ubuntu image for the basetool release (<a
href="https://github.com/microsoft/mu_basecore/pull/467">#467</a>)</li>
<li><a
href="251b9e5b3c">251b9e</a>
MdeModule: resolve invalid library override (<a
href="https://github.com/microsoft/mu_basecore/pull/469">#469</a>)</li>
<li><a
href="68dc947c0f">68dc94</a>
Use the new release of Linux base tools (<a
href="https://github.com/microsoft/mu_basecore/pull/471">#471</a>)</li>
<li><a
href="0ce0e478a3">0ce0e4</a>
BaseTools: make sure the got is empty</li>
<li><a
href="ea46190238">ea4619</a>
MdePkg: don"t set visibility to hidden</li>
<li><a
href="e7bbe590c4">e7bbe5</a>
BaseTools: remove WinNtInclude.h</li>
<li><a
href="6b6714a6d2">6b6714</a>
BaseTools: remove duplicate includes: <arch>/ProcessorBind.h</li>
<li><a
href="af5d498436">af5d49</a>
BaseTools: remove duplicate includes: IndustryStandard/Acpi*.h</li>
<li><a
href="5e57ed8e10">5e57ed</a>
MdePkg/PeImage.h: add bits from BaseTools version</li>
<li><a
href="e1827d5f06">e1827d</a>
BaseTools: drop IMAGE_FILE_MACHINE_ARM hacks</li>
<li><a
href="0292d8ff81">0292d8</a>
BaseTools: switch from EFI_IMAGE_MACHINE_* to IMAGE_FILE_MACHINE_*</li>
<li><a
href="faed40c7da">faed40</a>
BaseTools: remove duplicate includes: IndustryStandard/PeImage.h</li>
<li><a
href="7c6d66146b">7c6d66</a>
BaseTools: remove duplicate includes: IndustryStandard/*.h</li>
<li><a
href="595e2e3fcb">595e2e</a>
BaseTools: Add missing MU_CHANGEs</li>
<li><a
href="10771731f8">107717</a>
BaseTools: Remove /NXCOMPAT VS X64 DLINK flags (<a
href="https://github.com/microsoft/mu_basecore/pull/468">#468</a>)</li>
<li><a
href="5d25cbf16d">5d25cb</a>
BaseTools: Use latest release (<a
href="https://github.com/microsoft/mu_basecore/pull/472">#472</a>)</li>
<li><a
href="f066a0026b">f066a0</a>
[CodeQL] CryptoPkg: BaseCryptLib: Check return value from
`ASN1_get_object` (<a
href="https://github.com/microsoft/mu_basecore/pull/470">#470</a>)</li>
</ul>
</details>
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
Update platform CI and .devcontainer to use the project MU dev
containers. For more information see
https://github.com/microsoft/mu_devops/tree/main/Containers.
- [ ] Impacts functionality?
- [ ] Impacts security?
- [ ] Breaking change?
- [ ] Includes tests?
- [ ] Includes documentation?
## How This Was Tested
Local tests and CI pipeline
## Integration Instructions
N/A
# Preface
Please ensure you have read the [contribution
docs](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md) prior
to submitting the pull request. In particular,
[pull request
guidelines](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md#pull-request-best-practices).
## Description
This change added the SBSA builds on self-hosted ARM systems. This work
was left out because we need a change from BaseTools to resolve a build
break when using native ARM gcc compiler, which we have now in 202302
mu_basecore.
This change resolves
https://github.com/microsoft/mu_basecore/issues/369.
For each item, place an "x" in between `[` and `]` if true. Example:
`[x]`.
_(you can also check items in the GitHub UI)_
- [x] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
on an a separate Web page, ...
## How This Was Tested
Pipeline builds and run passes.
## Integration Instructions
N/A
# Preface
Please ensure you have read the [contribution
docs](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md) prior
to submitting the pull request. In particular,
[pull request
guidelines](https://github.com/microsoft/mu/blob/master/CONTRIBUTING.md#pull-request-best-practices).
## Description
Update OEM sample repo to **v2023020000.0.2** and mu_feature_config repo
to **v0.3.4** for mu_tiano_platforms.
The corresponding configuration module usage is also simplified to pair
with the submodule changes.
For each item, place an "x" in between `[` and `]` if true. Example:
`[x]`.
_(you can also check items in the GitHub UI)_
- [x] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [x] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
on an a separate Web page, ...
## How This Was Tested
Tested locally on Q35 and SBSA.
## Integration Instructions
Added a new configuration build variable for profile names on Q35
platform.
## Description
Update MU_BASECORE submodule. Main changes are the base tools binary
updates.
For each item, place an "x" in between `[` and `]` if true. Example:
`[x]`.
_(you can also check items in the GitHub UI)_
- [ ] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
on an a separate Web page, ...
## How This Was Tested
CI
## Integration Instructions
N/A
dependabot[bot]
Project Mu UEFI Bot [bot]
Michael Kubacki
Project Mu Bot
Project Mu Bot [bot]
Taylor Beebe
Chris Fernald
Doug Flick
Joey Vagedes
kenlautner
kuqin12