docs: fix grammatical error in Buffer Map API documentation #9434
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
Collaborator
|
@Navadeep0007 is not a repository collaborator. To proceed:
|
Remove redundant word 'pointer' in xrt::bo::map() description. Fixes Xilinx#8796 Signed-off-by: Navadeep0007 <[email protected]>
Navadeep0007
force-pushed
the
docs-fix-map-api-typo
branch
from
b5154c3 to
c365333
Compare
Author
|
Hi @gbuildx, I have fixed the DCO issue. |
Collaborator
|
@Navadeep0007 is not a repository collaborator. To proceed:
|
Collaborator
|
@Navadeep0007 I am not following what this change is changing? Is it adding a new file? What file is changed? |
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.
Remove redundant word 'pointer' in xrt::bo::map() description.
Fixes #8796
Problem solved by the commit
Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered
How problem was solved, alternative solutions (if any) and why they were rejected
Risks (if any) associated the changes in the commit
What has been tested and how, request additional testing if necessary
Documentation impact (if any)