On 7/15/25 11:25, Mark Cave-Ayland wrote:
Update the VFIOContainer declaration so that it is closer to our coding
guidelines: emove the explicit typedef (this is already handled by the
OBJECT_DECLARE_TYPE() macro) and add a blank line after the parent object.

Signed-off-by: Mark Cave-Ayland <[email protected]>


Reviewed-by: Cédric Le Goater <[email protected]>

Thanks,

C.


---
  include/hw/vfio/vfio-container.h | 5 +++--
  1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/include/hw/vfio/vfio-container.h b/include/hw/vfio/vfio-container.h
index 21e5807e48..50c91788d5 100644
--- a/include/hw/vfio/vfio-container.h
+++ b/include/hw/vfio/vfio-container.h
@@ -25,13 +25,14 @@ typedef struct VFIOGroup {
      bool ram_block_discard_allowed;
  } VFIOGroup;
-typedef struct VFIOContainer {
+struct VFIOContainer {
      VFIOContainerBase bcontainer;
+
      int fd; /* /dev/vfio/vfio, empowered by the attached groups */
      unsigned iommu_type;
      QLIST_HEAD(, VFIOGroup) group_list;
      VFIOContainerCPR cpr;
-} VFIOContainer;
+};
OBJECT_DECLARE_SIMPLE_TYPE(VFIOContainer, VFIO_IOMMU_LEGACY);


Reply via email to