Include the Integrity usage flag states [OTA-266] #1209
Merged
Conversation
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
fpezzinosn
requested review from
a team,
notoriaga and
silverjam
as code owners
silverjam
approved these changes
Aug 17, 2022
notoriaga
approved these changes
Aug 17, 2022
RReichert
approved these changes
Aug 18, 2022
fpezzinosn
force-pushed
the
fpezzinosn/OTA-266
branch
from
0fcc6eb to
6c1c5e3
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
@swift-nav/devinfra
Updates the Integrity usage flag states description for MSG_SSR_HIGH_LEVEL (3001)
API compatibility
Does this change introduce a API compatibility risk?
No, it only updates documentation
API compatibility plan
If the above is "Yes", please detail the compatibility (or migration) plan:
JIRA Reference
https://swift-nav.atlassian.net/browse/OTA-266