vhost-device/staging
Matias Ezequiel Vara Larsen 4742cf1a28 sound/pipewire: stop threadloop during drop
The threadloop has to be stopped only when the audio backend is dropped
otherwise release() stops it and it is not started again. The threadloop
must be active all alone the life of the audio backend.

Signed-off-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
2023-12-05 14:14:47 +02:00
..
vhost-device-sound sound/pipewire: stop threadloop during drop 2023-12-05 14:14:47 +02:00
vhost-device-video vhost-device: Don't return bool unnecessarily 2023-12-01 09:40:52 +01:00
.gitignore Add new workspace under staging/ subdirectory 2023-10-11 16:25:00 +05:30
Cargo.lock build(deps): bump the vhost-device group in /staging with 4 updates 2023-12-04 10:52:14 +05:30
Cargo.toml video: initial skeleton 2023-10-24 11:17:33 +02:00
coverage_config_x86_64.json sound/test: add tests for virtio_sound.rs 2023-11-09 09:50:39 +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.