Re: [PATCH v3 1/3] acpi: HMAT support in acpi_parse_entries_array()

On Sat, Dec 16, 2017 at 2:57 AM, Dan Williams wrote: > On Fri, Dec 15, 2017 at 5:53 PM, Rafael J. Wysocki wrote: >> On Friday, December 15, 2017 2:10:17 AM CET Dan Williams wrote: >>> On Wed, Dec 13, 2017 at 6:10 PM, Ross Zwisler >>>

Re: [PATCH v3 1/3] acpi: HMAT support in acpi_parse_entries_array()

On Fri, Dec 15, 2017 at 5:53 PM, Rafael J. Wysocki wrote: > On Friday, December 15, 2017 2:10:17 AM CET Dan Williams wrote: >> On Wed, Dec 13, 2017 at 6:10 PM, Ross Zwisler >> wrote: >> > The current implementation of acpi_parse_entries_array()

Re: [PATCH v3 1/3] acpi: HMAT support in acpi_parse_entries_array()

On Friday, December 15, 2017 2:10:17 AM CET Dan Williams wrote: > On Wed, Dec 13, 2017 at 6:10 PM, Ross Zwisler > wrote: > > The current implementation of acpi_parse_entries_array() assumes that each > > subtable has a standard ACPI subtable entry of type struct > >

Re: [PATCH v3 1/3] acpi: HMAT support in acpi_parse_entries_array()

On Wed, Dec 13, 2017 at 6:10 PM, Ross Zwisler wrote: > The current implementation of acpi_parse_entries_array() assumes that each > subtable has a standard ACPI subtable entry of type struct > acpi_subtable_header. This standard subtable header has a one byte length

Re: [PATCH v3 1/3] acpi: HMAT support in acpi_parse_entries_array()

On Thu, Dec 14, 2017 at 3:10 AM, Ross Zwisler wrote: > The current implementation of acpi_parse_entries_array() assumes that each > subtable has a standard ACPI subtable entry of type struct > acpi_subtable_header. This standard subtable header has a one byte length

[PATCH v3 1/3] acpi: HMAT support in acpi_parse_entries_array()

The current implementation of acpi_parse_entries_array() assumes that each subtable has a standard ACPI subtable entry of type struct acpi_subtable_header. This standard subtable header has a one byte length followed by a one byte type. The HMAT subtables have to allow for a longer length so