Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

extensions/khr: Add VK_KHR_calibrated_timestamps #890

Merged
merged 1 commit into from
Mar 25, 2024

Conversation

MarijnS95
Copy link
Collaborator

Depends on #889

@MarijnS95 MarijnS95 force-pushed the khr-line-rasterization branch from 6cd3df3 to a7e10bb Compare March 25, 2024 19:45
Base automatically changed from khr-line-rasterization to master March 25, 2024 19:47
@MarijnS95 MarijnS95 force-pushed the khr-calibrated-timestamps branch from 90ff8be to e20469e Compare March 25, 2024 19:47
@MarijnS95 MarijnS95 merged commit 13aaf85 into master Mar 25, 2024
20 checks passed
@MarijnS95 MarijnS95 deleted the khr-calibrated-timestamps branch March 25, 2024 19:50
MarijnS95 added a commit that referenced this pull request Mar 31, 2024
…ing `vk::Device` argument

When introducing this new `VK_KHR_calibrated_timestamps` extension based
on `VK_EXT_calibrated_timestamps` in #890 in parallel to finalizing
and merging the `Instance`/`Device` separation in #734, I seem to have
missed an opportunity to use the newly available `self.handle` for this
extension from `struct Device`, instead leaving an unnecessary
`device: vk::Device` argument in place.
MarijnS95 added a commit that referenced this pull request Mar 31, 2024
…ing `vk::Device` argument (#898)

When introducing this new `VK_KHR_calibrated_timestamps` extension based
on `VK_EXT_calibrated_timestamps` in #890 in parallel to finalizing
and merging the `Instance`/`Device` separation in #734, I seem to have
missed an opportunity to use the newly available `self.handle` for this
extension from `struct Device`, instead leaving an unnecessary
`device: vk::Device` argument in place.
@MarijnS95 MarijnS95 added this to the Ash 0.38 milestone Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants