From: Raphael Norwitz <raphael.norwitz@nutanix.com>
To: Murilo Opsfelder Araujo <muriloo@linux.ibm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
"mopsfelder@gmail.com" <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_PPC64g
Date: Wed, 4 May 2022 23:44:52 +0000 [thread overview]
Message-ID: <20220430035943.GA12685@raphael-debian-dev> (raw)
In-Reply-To: <20220503180108.34506-1-muriloo@linux.ibm.com>
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: Raphael Norwitz <raphael.norwitz@nutanix.com>
> ---
> 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
>
prev parent reply other threads:[~2022-05-04 23: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
2022-05-04 23:44 ` Raphael Norwitz [this message]
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=20220430035943.GA12685@raphael-debian-dev \
--to=raphael.norwitz@nutanix.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 \
/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).