mirror of
https://github.com/Motorhead1991/qemu.git
synced 2025-07-27 20:33:54 -06:00
rust: qdev: make ObjectImpl a supertrait of DeviceImpl
In practice it has to be implemented always in order to access an implementation of ClassInitImpl<ObjectClass>. Make the relationship explicit in the code. Reviewed-by: Zhao Liu <zhao1.liu@intel.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
This commit is contained in:
parent
688c674158
commit
68da5402df
1 changed files with 2 additions and 2 deletions
|
@ -17,12 +17,12 @@ use crate::{
|
|||
callbacks::FnCall,
|
||||
cell::bql_locked,
|
||||
prelude::*,
|
||||
qom::{ClassInitImpl, ObjectClass, Owned},
|
||||
qom::{ClassInitImpl, ObjectClass, ObjectImpl, Owned},
|
||||
vmstate::VMStateDescription,
|
||||
};
|
||||
|
||||
/// Trait providing the contents of [`DeviceClass`].
|
||||
pub trait DeviceImpl {
|
||||
pub trait DeviceImpl: ObjectImpl {
|
||||
/// _Realization_ is the second stage of device creation. It contains
|
||||
/// all operations that depend on device properties and can fail (note:
|
||||
/// this is not yet supported for Rust devices).
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue