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

feat: add virtio-def crate for virtio definitions #1149

Merged
merged 9 commits into from
Apr 30, 2024
Merged

Conversation

mkroening
Copy link
Member

No description provided.

@mkroening mkroening force-pushed the virtio-def branch 4 times, most recently from c1ea040 to 343a3a5 Compare April 26, 2024 09:22
@mkroening mkroening marked this pull request as ready for review April 26, 2024 09:24
@mkroening mkroening self-assigned this Apr 26, 2024
@mkroening mkroening requested review from stlankes and cagatay-y and removed request for stlankes April 26, 2024 09:25
@@ -141,13 +142,13 @@ impl ComCfg {

/// Returns the device status field.
pub fn dev_status(&self) -> u8 {
unsafe { read_volatile(&self.com_cfg.status).try_into().unwrap() }
unsafe { read_volatile(&self.com_cfg.status).bits() }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason to return the underlying u8 instead of a DeviceStatus?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, we should do that! But the scope of this PR is just changing the underlying types without separate changes to the API that can happen later. :)

@mkroening mkroening added this pull request to the merge queue Apr 30, 2024
Merged via the queue into main with commit 643d612 Apr 30, 2024
13 checks passed
@mkroening mkroening deleted the virtio-def branch April 30, 2024 11:19
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.

3 participants