diff options
author | David Hildenbrand <david@redhat.com> | 2018-10-05 11:20:09 +0200 |
---|---|---|
committer | Eduardo Habkost <ehabkost@redhat.com> | 2018-10-24 06:44:59 -0300 |
commit | 7c63ba2055a0a27cdd6ae835f5964f7895d18edc (patch) | |
tree | 47b5726bf5680fc480b6377b6f2f65a7d5aa70da /hw/mem | |
parent | bfec23a0d1944f465dc8ee640394ae752fc0d4dd (diff) | |
download | qemu-7c63ba2055a0a27cdd6ae835f5964f7895d18edc.zip qemu-7c63ba2055a0a27cdd6ae835f5964f7895d18edc.tar.gz qemu-7c63ba2055a0a27cdd6ae835f5964f7895d18edc.tar.bz2 |
memory-device: fix alignment error message
We're missing "x" after the leading 0.
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20181005092024.14344-2-david@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Diffstat (limited to 'hw/mem')
-rw-r--r-- | hw/mem/memory-device.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/hw/mem/memory-device.c b/hw/mem/memory-device.c index 6de4f70..0b52fe2 100644 --- a/hw/mem/memory-device.c +++ b/hw/mem/memory-device.c @@ -120,7 +120,7 @@ uint64_t memory_device_get_free_addr(MachineState *ms, const uint64_t *hint, /* address_space_start indicates the maximum alignment we expect */ if (QEMU_ALIGN_UP(address_space_start, align) != address_space_start) { - error_setg(errp, "the alignment (0%" PRIx64 ") is not supported", + error_setg(errp, "the alignment (0x%" PRIx64 ") is not supported", align); return 0; } |