[CODEOWNERS] Cleanup CODEOWNERS for non-AMD specific components#2180
Open
chinmaydd wants to merge 3 commits intoamd-stagingfrom
Open
[CODEOWNERS] Cleanup CODEOWNERS for non-AMD specific components#2180chinmaydd wants to merge 3 commits intoamd-stagingfrom
chinmaydd wants to merge 3 commits intoamd-stagingfrom
Conversation
chinmaydd
commented
Apr 13, 2026
Collaborator
|
I'd guess the MLIR people probably don't want to be notified of our merges either |
chinmaydd
changed the title
Collaborator
Author
|
ping |
lamb-j
approved these changes
Apr 14, 2026
Updates to llvm components generated for merges often sends notifications to upstream (non-AMD) codeowners. This should be avoided as part of our fork.
chinmaydd
force-pushed
the
users/chinmaydd/update-codeowners
branch
from
dbbef5d to
16896b4
Compare
Collaborator
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
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.
Updates to llvm components generated for merges often sends notifications to upstream (non-AMD) codeowners. This should be avoided as part of our fork.