Buffer location property for USM device allocation #46
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
sherry-yuan
force-pushed
the
usm_buffer_loc
branch
2 times, most recently
from
a40c7a5 to
397a189
Compare
pcolberg
suggested changes
Jan 26, 2022
pcolberg
suggested changes
Jan 26, 2022
|
I think something is going wrong with my permission of accessing klocwork. (see klocwork scans) |
No worries, the runner machine had been rebooted and the network connection temporarily failed when the workflow run launched. I restarted the workflow and it seems fine now. |
pcolberg
force-pushed
the
usm_buffer_loc
branch
from
7946195 to
cd50dbd
Compare
pcolberg
approved these changes
Jan 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 currently rebased upon buffer_location branch.
Related PR: #34 (34 has to be merged in first)