From: Peter Krempa <pkrempa@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: libvir-list@redhat.com, qemu-arm@nongnu.org,
qemu-devel@nongnu.org,
Andrew Baumann <Andrew.Baumann@microsoft.com>
Subject: Re: [PATCH] docs/system: Deprecate raspi2/raspi3 machine aliases
Date: Mon, 19 Oct 2020 10:54:31 +0200 [thread overview]
Message-ID: <20201019085431.GF3081357@angien.pipo.sk> (raw)
In-Reply-To: <20201019082121.1544550-1-f4bug@amsat.org>
On Mon, Oct 19, 2020 at 10:21:21 +0200, Philippe Mathieu-Daudé wrote:
> Since commit aa35ec2213b ("hw/arm/raspi: Use more
> specific machine names") the raspi2/raspi3 machines
> have been renamed as raspi2b/raspi3b.
>
> As more Raspberry Pi 2/3 models are emulated, in order
> to avoid confusion deprecate the raspi2/raspi3 machine
> aliases.
>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> docs/system/deprecated.rst | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/docs/system/deprecated.rst b/docs/system/deprecated.rst
> index 905628f3a0c..f0c7aaeb2ff 100644
> --- a/docs/system/deprecated.rst
> +++ b/docs/system/deprecated.rst
> @@ -355,6 +355,11 @@ This machine has been renamed ``fuloong2e``.
> These machine types are very old and likely can not be used for live migration
> from old QEMU versions anymore. A newer machine type should be used instead.
>
> +Raspberry Pi ``raspi2`` and ``raspi3`` machines (since 5.2)
> +'''''''''''''''''''''''''''''''''''''
> +
> +These machines have been respectively renamed ``raspi2b`` and ``raspi3b``.
> +
libvirt doesn't do any interpretation for these machine types, so we
don't need to add any compatibility. Obviously users of these machine
types might end up with broken configs if they were using them, but
that's qemu's decision.
On behalf of libvirt:
ACKed-by: Peter Krempa <pkrempa@redhat.com>
next prev parent reply other threads:[~2020-10-19 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 8:21 [PATCH] docs/system: Deprecate raspi2/raspi3 machine aliases Philippe Mathieu-Daudé
2020-10-19 8:29 ` Philippe Mathieu-Daudé
2020-10-19 8:54 ` Peter Krempa [this message]
2020-10-26 17:06 ` Philippe Mathieu-Daudé
2020-10-30 14:33 ` Peter Maydell
2020-10-30 15:52 ` Philippe Mathieu-Daudé
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=20201019085431.GF3081357@angien.pipo.sk \
--to=pkrempa@redhat.com \
--cc=Andrew.Baumann@microsoft.com \
--cc=f4bug@amsat.org \
--cc=libvir-list@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@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).