On 9/5/25 2:06 PM, Jason Gunthorpe wrote:
To avoid some internal padding.
Signed-off-by: Jason Gunthorpe <jgg@xxxxxxxxxx>
---
drivers/iommu/iommu.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
index 1874bbdc73b75e..543d6347c0e5e3 100644
--- a/drivers/iommu/iommu.c
+++ b/drivers/iommu/iommu.c
@@ -58,13 +58,13 @@ struct iommu_group {
void *iommu_data;
void (*iommu_data_release)(void *iommu_data);
char *name;
- int id;
struct iommu_domain *default_domain;
struct iommu_domain *blocking_domain;
struct iommu_domain *domain;
struct list_head entry;
- unsigned int owner_cnt;
void *owner;
+ unsigned int owner_cnt;
+ int id;
/* Used by the device_group() callbacks */
u32 bus_data;
ok, but still leaves a 32-bit hole at the end, which would occur in the struct if bus_data was put after id or owner_cnt.
Reviewed-by: Donald Dutile <ddutile@xxxxxxxxxx>
