From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Nicholas Piggin <npiggin@gmail.com>, qemu-ppc@nongnu.org
Cc: "David Gibson" <david@gibson.dropbear.id.au>,
"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Cédric Le Goater" <clg@kaod.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/4] hw/ppc/spapr: Rename 'softmmu'
Date: Thu, 18 Jan 2024 16:16:29 +0100 [thread overview]
Message-ID: <cb1b39b3-52e0-451e-b07b-ca8c9613a32a@linaro.org> (raw)
In-Reply-To: <20240118133206.158453-1-npiggin@gmail.com>
On 18/1/24 14:32, Nicholas Piggin wrote:
> I grabbed Philippe's series series and tried to use a more
> agreeable name. Further disagreement is okay, but must come
> with a better alternative :) would be good to get this out of
> the way. I actually don't think softmmu is a great term for it
> either even in isolation, so would be good to move away from it.
Eh thanks for the respin Nicholas! I'm happy with the new name :)
Series:
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
prev parent reply other threads:[~2024-01-18 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 13:32 [PATCH v2 0/4] hw/ppc/spapr: Rename 'softmmu' Nicholas Piggin
2024-01-18 13:32 ` [PATCH v2 1/4] hw/ppc/spapr: Add missing license Nicholas Piggin
2024-01-18 13:32 ` [PATCH v2 2/4] hw/ppc/spapr_hcall: Allow elision of softmmu_resize_hpt_prep Nicholas Piggin
2024-01-18 13:32 ` [PATCH v2 3/4] hw/ppc/spapr_hcall: Rename {softmmu -> vhyp_mmu}_resize_hpt_pr Nicholas Piggin
2024-01-18 13:32 ` [PATCH v2 4/4] hw/ppc/spapr: Rename 'softmmu' -> 'vhyp_mmu' Nicholas Piggin
2024-01-18 15:16 ` Philippe Mathieu-Daudé [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=cb1b39b3-52e0-451e-b07b-ca8c9613a32a@linaro.org \
--to=philmd@linaro.org \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.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).