DepSurf

Struct: acpi_dmar_device_scope

Status

Regular

• In 4.4: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In 4.8: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In 4.10: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In 4.13: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In 4.15: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In 4.18: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In 5.0: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In 5.3: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In 5.4: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In 5.8: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In 5.11: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In 5.13: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In 5.15: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In 5.19: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In 6.2: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In 6.5: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In 6.8: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

Arch

• In arm64: Absent ⚠️
• In armhf: Absent ⚠️
• In ppc64el: Absent ⚠️
• In riscv64: Absent ⚠️

Flavor

• In aws: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In azure: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In gcp: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

• In lowlatency: ✅

  struct acpi_dmar_device_scope {
      u8 entry_type;
      u8 length;
      u16 reserved;
      u8 enumeration_id;
      u8 bus;
  };
  

Differences

Regular

• No changes between 4.4 and 4.8 ✅
• No changes between 4.8 and 4.10 ✅
• No changes between 4.10 and 4.13 ✅
• No changes between 4.13 and 4.15 ✅
• No changes between 4.15 and 4.18 ✅
• No changes between 4.18 and 5.0 ✅
• No changes between 5.0 and 5.3 ✅
• No changes between 5.3 and 5.4 ✅
• No changes between 5.4 and 5.8 ✅
• No changes between 5.8 and 5.11 ✅
• No changes between 5.11 and 5.13 ✅
• No changes between 5.13 and 5.15 ✅
• No changes between 5.15 and 5.19 ✅
• No changes between 5.19 and 6.2 ✅
• No changes between 6.2 and 6.5 ✅
• No changes between 6.5 and 6.8 ✅

Arch

Flavor

• No changes between generic and aws ✅
• No changes between generic and azure ✅
• No changes between generic and gcp ✅
• No changes between generic and lowlatency ✅