[SYCL] Fix HIP plugin codeowners #10580
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
Signed-off-by: Larsen, Steffen <steffen.larsen@intel.com>
|
@intel/llvm-reviewers-cuda, are you okay to own HIP plug-in code? |
npmiller
approved these changes
Jul 26, 2023
bader
approved these changes
Jul 26, 2023
mdtoguchi
pushed a commit
to mdtoguchi/llvm
that referenced
this pull request
Oct 18, 2023
HIP plugin codeownership currently falls to L0 reviewers. A more appropriate group for owning this plugin is the CUDA plugin maintainers. In the future we can consider splitting the ownership or rename the CUDA reviewers group to encapsulate both. Signed-off-by: Larsen, Steffen <steffen.larsen@intel.com>
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.
HIP plugin codeownership currently falls to L0 reviewers. A more appropriate group for owning this plugin is the CUDA plugin maintainers. In the future we can consider splitting the ownership or rename the CUDA reviewers group to encapsulate both.