On Wed, 27 Feb 2019 15:51:00 +0800 Wei Yang <richardw.y...@linux.intel.com> wrote:
> The IO range is defined to 4 bytes with NVDIMM_ACPI_IO_LEN, so it is > more proper to use this macro instead of calculating it by sizeof. > > Signed-off-by: Wei Yang <richardw.y...@linux.intel.com> Reviewed-by: Igor Mammedov <imamm...@redhat.com> > --- > hw/acpi/nvdimm.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/hw/acpi/nvdimm.c b/hw/acpi/nvdimm.c > index e63a1ef15d..2457c1aa44 100644 > --- a/hw/acpi/nvdimm.c > +++ b/hw/acpi/nvdimm.c > @@ -992,7 +992,7 @@ static void nvdimm_build_common_dsm(Aml *dev) > field = aml_field(NVDIMM_DSM_IOPORT, AML_DWORD_ACC, AML_NOLOCK, > AML_PRESERVE); > aml_append(field, aml_named_field(NVDIMM_DSM_NOTIFY, > - sizeof(uint32_t) * BITS_PER_BYTE)); > + NVDIMM_ACPI_IO_LEN * BITS_PER_BYTE)); > aml_append(method, field); > > /*
