SecurityPkg: Improve formatting of msg when GetVariable fails #6477
Conversation
This file contains 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
Improve the formatting of the error message when GetVariable fails: start the message with an upper-case character, and close the quotes around the variable name. Signed-off-by: Rebecca Cran <rebecca@bsdio.com>
bexcran
force-pushed
the
secure-boot-provision-error-msg-formatting
branch
from
a9e8054
to
90ad6ee
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Improve the formatting of the error message when GetVariable fails: start the message with an upper-case character, and close the quotes around the variable name.
How This Was Tested
Verified the error message was formatted better after the change.
Integration Instructions
N/A