diff options
| author | Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru> | 2025-04-09 11:42:31 +0300 |
|---|---|---|
| committer | Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru> | 2025-05-01 12:12:19 +0300 |
| commit | b836bf2ab68fbc1e253c10bee95fa36399762967 (patch) | |
| tree | 031aadc2e180db69f94801dcea627abf1feeef78 /rust/qemu-api/src/assertions.rs | |
| parent | da17dd5c5ee8e33124da0bf91aed11491d0c04de (diff) | |
| download | focaccia-qemu-b836bf2ab68fbc1e253c10bee95fa36399762967.tar.gz focaccia-qemu-b836bf2ab68fbc1e253c10bee95fa36399762967.zip | |
qapi/block-core: deprecate some block-job- APIs
For change, pause, resume, complete, dismiss and finalize actions corresponding job- and block-job commands are almost equal. The difference is in find_block_job_locked() vs find_job_locked() functions. What's different? 1. find_block_job_locked() checks whether the found job is a block-job. This is OK when moving to more generic API, no needs to document this change. 2. find_block_job_locked() reports DeviceNotActive on failure, when find_job_locked() reports GenericError. So, let's document this difference in deprecated.txt. Still, for dismiss and finalize errors are not documented at all, so be silent in deprecated.txt as well. ACKed-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Reviewed-by: Markus Armbruster <armbru@redhat.com> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru> Message-ID: <20250409084232.28201-3-vsementsov@yandex-team.ru>
Diffstat (limited to 'rust/qemu-api/src/assertions.rs')
0 files changed, 0 insertions, 0 deletions