vhost-device/staging
Manos Pitsidianakis aa16ef0699 sound/pipewire: handle StreamWithIdNotFound consistently
When handling controlq messages, handle StreamWithIdNotFound the same
way on all methods:

- if we are passed a &mut ControlMessage, set it to
  VIRTIO_SND_S_BAD_MSG.
- if we are passed a stream_id, return StreamWithIdNotFound.

Signed-off-by: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
2023-10-24 11:08:26 +01:00
..
vhost-device-sound sound/pipewire: handle StreamWithIdNotFound consistently 2023-10-24 11:08:26 +01:00
vhost-device-video video: add v4l2 mocks 2023-10-24 11:17:33 +02:00
.gitignore Add new workspace under staging/ subdirectory 2023-10-11 16:25:00 +05:30
Cargo.lock video: add v4l2-decoder backend 2023-10-24 11:17:33 +02:00
Cargo.toml video: initial skeleton 2023-10-24 11:17:33 +02:00
coverage_config_x86_64.json sound/test: add testing module for sound 2023-10-20 18:35:29 +05:30
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.