[LR2021] a fix for reverse order of bytes in OOK sync word#1722
Merged
jgromes merged 2 commits intojgromes:masterfrom Mar 14, 2026
Merged
[LR2021] a fix for reverse order of bytes in OOK sync word#1722jgromes merged 2 commits intojgromes:masterfrom
jgromes merged 2 commits intojgromes:masterfrom
Conversation
Owner
|
Thanks for the contribution! Looking at the code, we should probably add a check that |
Contributor
Author
|
I am not certain of your intention, sorry. |
Owner
|
Added the check and merged - thanks for the contribution! |
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.
This is a successor of previously applied PR #1686 that was relevant to GFSK code.
The same issue remains in OOK code.
This PR is intended to fix it.