-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spec: Fix formatting of example of memory port types. #2368
Merged
mergify
merged 2 commits into
chipsalliance:master
from
richardxia:fix-spec-memory-code-example
Sep 24, 2021
Merged
spec: Fix formatting of example of memory port types. #2368
mergify
merged 2 commits into
chipsalliance:master
from
richardxia:fix-spec-memory-code-example
Sep 24, 2021
Conversation
This file contains 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
8abf308 reordered the fields, but it unintentionally placed a closing brace before the actual end of the write port type. This moves the brace to the end of the port.
seldridge
approved these changes
Sep 24, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whoops. Thanks for the fix, @richardxia!
mergify bot
pushed a commit
that referenced
this pull request
Sep 24, 2021
8abf308 reordered the fields, but it unintentionally placed a closing brace before the actual end of the write port type. This moves the brace to the end of the port. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit b2cae19) # Conflicts: # spec/spec.pdf
mergify bot
pushed a commit
that referenced
this pull request
Sep 24, 2021
8abf308 reordered the fields, but it unintentionally placed a closing brace before the actual end of the write port type. This moves the brace to the end of the port. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit b2cae19) # Conflicts: # spec/spec.pdf
mergify bot
pushed a commit
that referenced
this pull request
Sep 24, 2021
8abf308 reordered the fields, but it unintentionally placed a closing brace before the actual end of the write port type. This moves the brace to the end of the port. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit b2cae19) # Conflicts: # spec/spec.pdf
mergify bot
added a commit
that referenced
this pull request
Sep 24, 2021
8abf308 reordered the fields, but it unintentionally placed a closing brace before the actual end of the write port type. This moves the brace to the end of the port. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit b2cae19) # Conflicts: # spec/spec.pdf Co-authored-by: Richard Xia <rxia@sifive.com>
mergify bot
added a commit
that referenced
this pull request
Sep 24, 2021
8abf308 reordered the fields, but it unintentionally placed a closing brace before the actual end of the write port type. This moves the brace to the end of the port. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit b2cae19) # Conflicts: # spec/spec.pdf Co-authored-by: Richard Xia <rxia@sifive.com>
mergify bot
added a commit
that referenced
this pull request
Sep 24, 2021
8abf308 reordered the fields, but it unintentionally placed a closing brace before the actual end of the write port type. This moves the brace to the end of the port. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit b2cae19) # Conflicts: # spec/spec.pdf Co-authored-by: Richard Xia <rxia@sifive.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Backported
This PR has been backported to marked stable branch
Please Merge
Accepted PRs that are ready to be merged. Useful when waiting on CI.
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.
8abf308 reordered the fields, but it
unintentionally placed a closing brace before the actual end of the write
port type. This moves the brace to the end of the port.
Before
(Note that the page break happens at the worst possible position, since it happens to be right where stray closing brace is)
After
Contributor Checklist
Type of Improvement
API Impact
No API changes (unless if people treat typos in the spec too literally)
Backend Code Generation Impact
No code changes.
Desired Merge Strategy
Squash: The PR will be squashed and merged (choose this if you have no preference.
Release Notes
Fixes a minor typo in the FIRRTL language memory specification document, where a closing brace was placed before the actual end of the write port type.
Reviewer Checklist (only modified by reviewer)
Please Merge
?