Bumps MU_BASECORE from `2023020006.3.1` to `2023020007.0.0`
Introduces 3 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
Current script will try to update the mcopy configuration file. After
QEMU run, the build script will then try to open the virtual disk
indicated in this configuration. When there are multiple building
instances on the same Linux system, we could end up with various
conflicts, either opening up the incorrect image file, or opened up a
file from other build jobs.
This change attempts to fix it by initiating a configuration file for
each build for reference and update the environment variable to set up
the configuration.
- [ ] 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 was tested on both selfhost agents internal and here on the public
pipeline builds.
## Integration Instructions
N/A.
---------
Co-authored-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps Common/MU from `2023020001.5.0` to `2023020001.5.1`
Introduces 10 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps Features/CONFIG from `2.0.0` to `2.0.2`
Introduces 15 new commits in
[Features/CONFIG](https://github.com/microsoft/mu_feature_config.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Co-authored-by: Michael Kubacki <michael.kubacki@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
There has been build failures observed on selfhosted pipelines running
on AARCH64 systems. It was due to the rust setup we recently added.
The failure on the surface was because the build process will try to
install x86_64 toolchain on AARCH64 systems. This change will remove the
extra steps for selfhosted agent runs as those environments should be
preset properly.
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
This is tested on both internal and external pipelines.
## Integration Instructions
N/A
Bumps Common/MU_OEM_SAMPLE from `2023020000.0.5` to `2023020000.0.6`
Introduces 15 new commits in
[Common/MU_OEM_SAMPLE](https://github.com/microsoft/mu_oem_sample.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps [xmlschema](https://github.com/sissaschool/xmlschema) from 2.4.0
to 2.5.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/sissaschool/xmlschema/releases">xmlschema's
releases</a>.</em></p>
<blockquote>
<h2>v2.5.0 (2023-09-21)</h2>
<ul>
<li>Fix identity keys tracking with additional full XPath checks on XML
data</li>
<li>Rewrite schema exports using relative paths</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/sissaschool/xmlschema/blob/master/CHANGELOG.rst">xmlschema's
changelog</a>.</em></p>
<blockquote>
<h1><code>v2.5.0</code>_ (2023-09-21)</h1>
<ul>
<li>Fix identity keys tracking with additional full XPath checks on XML
data</li>
<li>Rewrite schema exports using relative paths</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="05af170a3f"><code>05af170</code></a>
Fix weak filepaths in test_pl_validation_translation</li>
<li><a
href="11f4b43943"><code>11f4b43</code></a>
Add pyproject.toml</li>
<li><a
href="9d8963c880"><code>9d8963c</code></a>
Merge and fix translation tests module</li>
<li><a
href="785dbea128"><code>785dbea</code></a>
Update release info</li>
<li><a
href="eac7eb06dc"><code>eac7eb0</code></a>
Detach schema export as a function in a new module</li>
<li><a
href="866ed43587"><code>866ed43</code></a>
Fix schema export on MacOS and Windows</li>
<li><a
href="ff1a6489dc"><code>ff1a648</code></a>
Update CI and Tox config</li>
<li><a
href="ea3967af6f"><code>ea3967a</code></a>
Bump minor release</li>
<li><a
href="16cfd1bd6b"><code>16cfd1b</code></a>
Fix style and static typing errors</li>
<li><a
href="3a83e9fd47"><code>3a83e9f</code></a>
Replace exported locations with relative paths (issue <a
href="https://redirect.github.com/sissaschool/xmlschema/issues/362">#362</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/sissaschool/xmlschema/compare/v2.4.0...v2.5.0">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
You can trigger a rebase of this PR by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
## Description
VariablePolicyFuncTestApp now passes on Q35 and SBSA.
- [ ] 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, ...
- [x] 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 in the CI pipelines
## Integration Instructions
N/A
Bumps MU_BASECORE from `2023020006.2.1` to `2023020006.2.2`
Introduces 1 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
* Update Sbsa PlatformBuild.py
* Pull in changes from Q35 PlatformBuild.py
* Remove redundant code
* Update import order and function comments in Q35 package.
- [ ] 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
* Validated the Sbsa package builds and boots to UEFI shell.
## Integration Instructions
N/A
## Description
The root is currently determined using `cwd()` which can cause the
root to be relative to the directory where the stuart command is
invoked from. It should always return the same absolute path so
`cwd()` is removed.
- [ ] 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
QemuQ35Pkg build from the root directory and subdirectories.
## Integration Instructions
N/A
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps MU_BASECORE from `2023020006.1.1` to `2023020006.2.1`
Introduces 9 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps MU_BASECORE from `2023020006.1.0` to `2023020006.1.1`
Introduces 5 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Adds a new GitHub workflow that allows CodeQL to run against platform
builds. Previously, only a "CI" CodeQL workflow existed that did not
support platform builders.
This file is being added directly to the repo as it is paired with
other changes that it has been tested alongside. In the future, it
will automatically be synced from mu_devops.
Nothing about the file is specific to mu_tiano_platforms or any
particular platform. It works by discovering all buildable platforms
in a repo before any dependencies are cloned and then verifying
the build files in the platform package directory support platform
build. If they do, it is checked if they support CodeQL. Only
platforms that meet all of these conditions are actually built via
a dynamic platform package matrix.
This allows the workflow to scale across platform repos and
automatically pick up new platforms as they onboard support for
CodeQL.
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Makes a number of adjustments in PlatformBuild.py as outlined below.
The main improvement is adding support to recursively gather CodeQL
filter files within the repo.
1. Remove unused imports at the top of the file.
2. Replace local functionality with common implementation in the
`codeql_helpers` module.
3. Remove trailing whitespace throughout the file.
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps Common/MU_TIANO from `2023020000.0.4` to `2023020000.1.0`
Introduces 2 new commits in
[Common/MU_TIANO](https://github.com/microsoft/mu_tiano_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps Common/MU from `2023020001.4.1` to `2023020001.5.0`
Introduces 2 new commits in
[Common/MU](https://github.com/microsoft/mu_plus.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps MU_BASECORE from `2023020006.0.0` to `2023020006.1.0`
Introduces 1 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
Bumps MU_BASECORE from `2023020005.0.1` to `2023020006.0.0`
Introduces 4 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
There are several errors produced when building QemuQ35Pkg and
QemuSbsaPkg indicating that some relative paths cannot be converted to
absolute paths. This is because these paths do not exist in the code
tree anymore.
This patch removes the unused env vars.
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
Still builds without these.
## Integration Instructions
N/A.
## Description
All header files should have include guards.
See the following for more info:
https://codeql.github.com/codeql-query-help/cpp/cpp-missing-header-guard/
- [ ] 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 build
- Ran CodeQL with `cpp-missing-header-guard` enabled
## Integration Instructions
N/A
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
## Description
The physical presence check is a poor way to determine if a user is
actually physically present at the machine. Because some security checks
can be bypassed with physical presence, set physical presence to FALSE.
- [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
Tested on Q35 and SBSA
## Integration Instructions
N/A
## Description
The virtual drive image is passed with the following parameter:
`-hdd <VirtualDrivePath>`
This results in the following warning:
```
WARNING: Image format was not specified for 'VirtualDrive.img' and
probing guessed raw.
Automatically detecting the format is dangerous for raw
images, write operations on block 0 will be restricted.
Specify the 'raw' format explicitly to remove the
restrictions.
```
This passes the image using `-drive` to resolve the warning.
- [ ] 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
- QemuQ35Pkg and QemuSbsaPkg build and run
## Integration Instructions
N/A
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Adds the driver to both packages to demonstrate a Rust based UEFI
DXE driver executing during boot on a X64 and AARCH64 system.
A workspace Cargo.toml file is added for cargo make. Since this repo
is the "leaf of a dependency chain" in that it builds binaries that
are integrated into the platform build, the `Cargo.lock` file is
checked in per the guidance in:
https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Adds files to support:
- A cargo-make makefile
- Default Rust toolchain version
- Rust formatting configuration
- Rust host-based unit test CI execution
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
## Description
Updates the repo for a change that merged UefiCpuLib with CpuLib.
UefiCpuLib will be removed entirely soon so all references are updated
to CpuLib.
Includes the following submodule updates:
- `MU_BASECORE` to `v2023020005.0.1`
- `Common/MU` to `v2023020001.4.1`
- `Common/MU_TIANO` to `v2023020001.4.1`
- `Features/MM_SUPV` to `v8.1.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
- CI package build (via PR checks)
## Integration Instructions
N/A
---
Associated Changes in Submodules
- https://github.com/microsoft/mu_feature_mm_supv/pull/164
- https://github.com/microsoft/mu_plus/pull/304
- https://github.com/microsoft/mu_tiano_plus/pull/174
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Bumps MU_BASECORE from `2023020003.0.1` to `2023020004.0.1`
Introduces 4 new commits in
[MU_BASECORE](https://github.com/microsoft/mu_basecore.git).
Signed-off-by: Project Mu Bot <mubot@microsoft.com>
## Description
- Added CpuInfoDxe driver that prints the basic information about the CPU
model invoked by QEMU.
- Added a command line argument to pass the CPU model to be used while
invoking QEMU
- Added basic tests to validate the CPU model being used
- [x] Impacts functionality?
Added a new driver that prints CPU model information
- [ ] Impacts security?
N/A
- [ ] Breaking change?
N/A
- [ ] Includes tests?
N/A
- [ ] Includes documentation?
No
## How This Was Tested
Validated the changes on QEMU
## Integration Instructions
N/A
## Description
The most recent changes in mu_plus fix the paging audit test failures on
SBSA. This PR pulls in the latest mu_plus, updates the paging audit
calls to reflect the new command line interface, and removes the
PagingAuditTestApp test failure exemption on SBSA.
- [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, ...
- [x] 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 in the pipelines
## Integration Instructions
N/A
Project Mu UEFI Bot [bot]
dependabot[bot]
Project Mu Bot [bot]
kuqin12
Taylor Beebe
Antaeus Kleinert-Strand
Michael Kubacki
Oliver Smith-Denny
Nishanth Sanjeevi