Skip to content

Conversation

phip1611
Copy link
Contributor

Summary of the PR

This is a backport of #322 [0] from the latest state to v0.12.1 to enable an easy way to use this in cloud-hypervisor by simply bumping the patch version of the component.

The backport is done in two steps, this is step 1/2. This commit only does the necessary steps for kvm-bindings.

[0] #322

This PR follows the strategy proposed by @roypat on Slack.

Requirements

Before submitting your PR, please make sure you addressed the following
requirements:

  • All commits in this PR have Signed-Off-By trailers (with
    git commit -s), and the commit message has max 60 characters for the
    summary and max 75 characters for each description line.
  • All added/changed functionality has a corresponding unit/integration
    test.
  • All added/changed public-facing functionality has entries in the "Upcoming
    Release" section of CHANGELOG.md (if no such section exists, please create one).
  • Any newly added unsafe code is properly documented.

@phip1611 phip1611 changed the base branch from main to kvm-bindings-v0.12.1 September 16, 2025 06:10
@phip1611 phip1611 force-pushed the backport-nested-kvm-state-from-kvm-bindings-v0.13.0-to-v0.12.1 branch from 43ef603 to 5c96af1 Compare September 16, 2025 06:43
This is a backport of rust-vmm#322 [0] from the latest state to
v0.12.1 to enable an easy way to use this in cloud-hypervisor
by simply bumping the patch version of the component.

The backport is done in two steps, this is step 1/2. This
commit only does the necessary steps for kvm-bindings.

[0] rust-vmm#322

Signed-off-by: Philipp Schuster <[email protected]>
On-behalf-of: SAP [email protected]
@phip1611 phip1611 force-pushed the backport-nested-kvm-state-from-kvm-bindings-v0.13.0-to-v0.12.1 branch from 5c96af1 to c902337 Compare September 16, 2025 06:53
@roypat roypat merged commit 395e838 into rust-vmm:kvm-bindings-v0.12.1 Sep 16, 2025
39 checks passed
@phip1611 phip1611 deleted the backport-nested-kvm-state-from-kvm-bindings-v0.13.0-to-v0.12.1 branch September 16, 2025 16:38
@phip1611
Copy link
Contributor Author

Nice! How do we continue with kvm-ioctls?

@roypat
Copy link
Member

roypat commented Sep 17, 2025

Nice! How do we continue with kvm-ioctls?

I published 0.12.1 to crates.io, so for kvm-ioctls, I created the kvm-ioctls-v0.22.1 branch, onto which we'll merge only the changes to kvm-ioctls, and where in Cargo.toml we remove the path dependency on kvm-bindings, and instead consume 0.12.1 from crates.io

@phip1611
Copy link
Contributor Author

Here we go #350

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