Update mdev type parsing to handle multiple spaces in type strings#65
Merged
cdesiniotis merged 1 commit intoNVIDIA:mainfrom Jul 28, 2025
Merged
Conversation
Contributor
Author
Signed-off-by: Michail Resvanis <mresvani@redhat.com>
9f6e7cd to
1c2d932
Compare
cdesiniotis
approved these changes
Jul 28, 2025
Contributor
cdesiniotis
left a comment
There was a problem hiding this comment.
Thanks for the contribution @mresvanis!
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
2 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.
This change updates the mdev type name parsing logic to consider multi-space strings (e.g.
NVIDIA RTX Pro 6000 Blackwell DC-8C), instead of relying on the name containing a single space (e.g.GRID A100-40C).Before this change:
After this change: