Improve VTRUST bits documentation and naming. #3741
Merged
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.
During a recent code review I was getting lost in the bitwise complement logic that is used for vtrust flags. This PR should improve legibility by renaming the code constants to what I believe to be more intuitive names and by adding more documentation.
VTRUST_ALL
->VTRUST_NO_WARNING
VTRUST_ALL
no longer represents "ultimate trust". It represents the absence of any vendor screen warnings.VTRUST_RED
- >VTRUST_NO_RED
etc.When the corresponding bit is set, it represents that no red screen should be shown, etc.