Clarify uart_write_blocking() API vs UART still busy sending (#1274) #1709
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
lurch
reviewed
May 21, 2024
lurch
added
documentation
Contributor
|
Nice 👍 |
Contributor
|
@kilograham Can we merge this? |
peterharperuk
force-pushed
the
1274-blocking-uart-transmission-appears-to-exit-early
branch
from
9f87ef0 to
478fc3f
Compare
Contributor
|
Needed a rebase |
kilograham
previously approved these changes
Jul 25, 2024
kilograham
approved these changes
Jul 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
A minor improvement to a comment: Clarify
uart_write_blocking()API vs UART still busy sending (#1274)