virtio-msg: eliminate non-ascii characters #23
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
Smart quotes and em-dashes snuck into the doc. Upstream seems to only use ASCII so eliminate these. Signed-off-by: Bill Mills <bill.mills@linaro.org>
bertrand-marquis
approved these changes
Jun 20, 2025
Collaborator
bertrand-marquis
left a comment
bertrand-marquis
left a comment
There was a problem hiding this comment.
Looks good to me
arnopo
approved these changes
Jun 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
RFC2 contains this patch squashed into the main commit.
Our file had smart quotes and em-dashes.
Upstream only uses ASCII.
I also adjusted the dashes to commas or semi-colons based on the situation.