MbedTlsPei - #280
Open
Aaron (apop5) wants to merge 2 commits into
Open
Conversation
mu-automation
Bot
added
the
impact:non-functional
Aaron (apop5)
force-pushed
the
personal/apop5/mbedtlspei
branch
from
August 20, 2026 21:29
4c99dda to
2ff176c
Compare
mu-automation
Bot
added
the
language:python
Collaborator
Author
|
note: this is dependent on release/202608 branch of mu_basecore |
Collaborator
Author
|
Create Markdown about this |
Aaron (apop5)
marked this pull request as ready for review
August 21, 2026 23:12
Sean Brogan (spbrogan)
approved these changes
Aug 21, 2026
Sean Brogan (spbrogan)
left a comment
Sean Brogan (spbrogan)
left a comment
Member
There was a problem hiding this comment.
might be nice to have a readme file with some details otherwise looks great.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
<Include a description of the change and why this change was made.>
For details on how to complete these options and their meaning refer to CONTRIBUTING.md.
How This Was Tested
<Describe the test(s) that were run to verify the changes.>
Integration Instructions
<Describe how these changes should be integrated. Use N/A if nothing is required.>