vhost-device/staging
Timos Ampelikiotis db63d2057c Move vhost-device-can on main workspace
Changes:
- Update socketcan-rs to v3.3.1 which solve the issue regarding the CANFD messages:
  - https://github.com/socketcan-rs/socketcan-rs/pull/61
- Update Cargo.lock files under main and staging workspace

Signed-off-by: Timos Ampelikiotis <t.ampelikiotis@virtualopensystems.com>
2024-11-14 05:29:54 +02:00
..
vhost-device-video build(deps): bump the vhost-device group in /staging with 6 updates 2024-11-11 10:08:30 +05:30
.gitignore Add new workspace under staging/ subdirectory 2023-10-11 16:25:00 +05:30
Cargo.lock Move vhost-device-can on main workspace 2024-11-14 05:29:54 +02:00
Cargo.toml Move vhost-device-can on main workspace 2024-11-14 05:29:54 +02:00
coverage_config_x86_64.json Move vhost-device-can on main workspace 2024-11-14 05:29:54 +02:00
README.md Add new workspace under staging/ subdirectory 2023-10-11 16:25:00 +05:30

vhost-device staging workspace

This directory includes a separate Cargo workspace to include working vhost-user backend implementations that concern devices that have partial functionality and devices (and/or functionality) not yet ratified in the VIRTIO specification. For more details about vhost-device you can refer to the repository README.

To add a new member crate:

  1. Place it under this directory, ./staging.
  2. Append its name in the workspace.members array field of the workspace manifest file.
  3. Update the crate list in the repository README.

Testing and Continuous Integration

Notice : The CI runs on the root workspace only. This means that staging crates can have failing tests and bring down code coverage without automatic checks. Tests can still be run locally as part of the development process. To add a crate to the CI, add it to the root Cargo.toml workspace.members array as well as the staging manifest.