From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Murilo Opsfelder Araujo <muriloo@linux.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org, mopsfelder@gmail.com,
Fabiano Rosas <farosas@linux.ibm.com>,
Raphael Norwitz <raphael.norwitz@nutanix.com>,
Peter Turschmid <peter.turschm@nutanix.com>
Subject: Re: [PATCH] vhost-user: Use correct macro name TARGET_PPC64
Date: Wed, 4 May 2022 18:45:27 -0300 [thread overview]
Message-ID: <0debc21d-fefa-bb7f-6fdc-3d542d463751@gmail.com> (raw)
In-Reply-To: <20220504165920-mutt-send-email-mst@kernel.org>
On 5/4/22 17:59, Michael S. Tsirkin wrote:
> On Tue, May 03, 2022 at 03:01:08PM -0300, Murilo Opsfelder Araujo wrote:
>> The correct name of the macro is TARGET_PPC64.
>>
>> Fixes: 27598393a232 ("Lift max memory slots limit imposed by vhost-user")
>> Reported-by: Fabiano Rosas <farosas@linux.ibm.com>
>> Signed-off-by: Murilo Opsfelder Araujo <muriloo@linux.ibm.com>
>> Cc: Raphael Norwitz <raphael.norwitz@nutanix.com>
>> Cc: Peter Turschmid <peter.turschm@nutanix.com>
>
> Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
>
> ok to merge through the ppc tree
Thanks for the r-b. Queued in gitlab.com/danielhb/qemu/tree/ppc-next.
Daniel
>
>> ---
>> hw/virtio/vhost-user.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/hw/virtio/vhost-user.c b/hw/virtio/vhost-user.c
>> index 9c4f84f35f..e356c72c81 100644
>> --- a/hw/virtio/vhost-user.c
>> +++ b/hw/virtio/vhost-user.c
>> @@ -51,7 +51,7 @@
>> #include "hw/acpi/acpi.h"
>> #define VHOST_USER_MAX_RAM_SLOTS ACPI_MAX_RAM_SLOTS
>>
>> -#elif defined(TARGET_PPC) || defined(TARGET_PPC_64)
>> +#elif defined(TARGET_PPC) || defined(TARGET_PPC64)
>> #include "hw/ppc/spapr.h"
>> #define VHOST_USER_MAX_RAM_SLOTS SPAPR_MAX_RAM_SLOTS
>>
>> --
>> 2.35.1
>
>
next prev parent reply other threads:[~2022-05-04 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 18:01 [PATCH] vhost-user: Use correct macro name TARGET_PPC64 Murilo Opsfelder Araujo
2022-05-03 18:16 ` Daniel Henrique Barboza
2022-05-04 20:42 ` Daniel Henrique Barboza
2022-05-04 20:59 ` Michael S. Tsirkin
2022-05-04 21:45 ` Daniel Henrique Barboza [this message]
2022-05-04 23:44 ` [PATCH] vhost-user: Use correct macro name TARGET_PPC64g Raphael Norwitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0debc21d-fefa-bb7f-6fdc-3d542d463751@gmail.com \
--to=danielhb413@gmail.com \
--cc=farosas@linux.ibm.com \
--cc=mopsfelder@gmail.com \
--cc=mst@redhat.com \
--cc=muriloo@linux.ibm.com \
--cc=peter.turschm@nutanix.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).