extensions/khr: Drop _khr suffix from get_memory_fd_properties_khr
#580
Conversation
This file contains 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
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 an erroneous suffix that's already captured in the module path of this item, and should be omitted everywhere. This method is the only offender besides the experimental AMD extensions.
Fixes: 98def0a ("Add
VK_KHR_external_memory_fdextension support (#270)")Draft because I want to shelve this for a bit until the next breaking release... We can probably get all the current extension additions and Vulkan 1.3 API out the door with a simple patch bump.