use caret requirements for rust-vmm crates

We should use caret requirements for crates that are not yet on
a major release. This helps with avoiding breaking changes
because for any crate specified as 0.x.y, when a new release
is available, cargo will only pick up new patch releases.

Related issues:
- rust-vmm/vm-memory#199
- rust-vmm/community#131

Signed-off-by: Andreea Florescu <[email protected]>

Author: andreeaflorescu

crates/virtio-queue/Cargo.toml

@@ -13,14 +13,14 @@ edition = "2018"
 test-utils = []
 
 [dependencies]
-vm-memory = ">=0.8.0"
-vmm-sys-util = ">=0.8.0"
-log = ">=0.4.6"
-virtio-bindings = { path="../virtio-bindings", version = ">=0.1.0" }
+vm-memory = "^0.8.0"
+vmm-sys-util = "^0.10.0"
+log = "^0.4.6"
+virtio-bindings = { path="../virtio-bindings", version = "^0.1.0" }
 
 [dev-dependencies]
 criterion = "0.3.0"
-vm-memory = { version = ">=0.8.0", features = ["backend-mmap", "backend-atomic"] }
+vm-memory = { version = "^0.8.0", features = ["backend-mmap", "backend-atomic"] }
 memoffset = "~0"
 
 [[bench]]