From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Michael Walle" <michael@walle.cc>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [PATCH] Deprecate lm32 port
Date: Wed, 23 Sep 2020 09:55:42 +0200 [thread overview]
Message-ID: <a1dda44f-e521-ef82-f5bc-7435c81fe888@redhat.com> (raw)
In-Reply-To: <20200827113259.25064-1-peter.maydell@linaro.org>
On 27/08/2020 13.32, Peter Maydell wrote:
> Deprecate our lm32 target support. Michael Walle (former lm32 maintainer)
> suggested that we do this in 2019:
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg605024.html
> because the only public user of the architecture is the many-years-dead
> milkymist project. (The Linux port to lm32 was never merged upstream.)
>
> In commit 4b4d96c776f552e (March 2020) we marked it as 'orphan' in
> the MAINTAINERS file, but didn't officially deprecate it. Mark it
> deprecated now, with the intention of removing it from QEMU in
> mid-2021 before the 6.1 release.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> Based-on: 20200825172719.19422-1-peter.maydell@linaro.org
> ("Deprecate Unicore32 port") to avoid the obvious textual-conflict.
>
> docs/system/deprecated.rst | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/docs/system/deprecated.rst b/docs/system/deprecated.rst
> index 4c52098c707..5c7fc8a3c99 100644
> --- a/docs/system/deprecated.rst
> +++ b/docs/system/deprecated.rst
> @@ -416,6 +416,14 @@ The above, converted to the current supported format::
> linux-user mode CPUs
> --------------------
>
> +``lm32`` CPUs (since 5.2.0)
> +'''''''''''''''''''''''''''
> +
> +The ``lm32`` guest CPU support is deprecated and will be removed in
> +a future version of QEMU. The only public user of this architecture
> +was the milkymist project, which has been dead for years; there was
> +never an upstream Linux port.
I was just looking at the current version of deprecated.rst (which has
this patch included), and could it be that it ended up in the wrong
section here? "lm32" is rather a softmmu target, not a linux-user mode CPU?
Thomas
next prev parent reply other threads:[~2020-09-23 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 11:32 [PATCH] Deprecate lm32 port Peter Maydell
2020-08-27 11:36 ` Daniel P. Berrangé
2020-08-27 12:02 ` Michael Walle
2020-08-31 20:08 ` Philippe Mathieu-Daudé
2020-08-27 13:52 ` Thomas Huth
2020-08-27 14:19 ` Peter Maydell
2020-08-27 14:50 ` Thomas Huth
2020-08-31 20:11 ` Philippe Mathieu-Daudé
2020-09-23 7:55 ` Thomas Huth [this message]
2020-09-23 9:47 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2020-10-12 15:33 [PATCH 00/10] target/arm: Various v8.1M minor features Peter Maydell
2020-10-12 15:33 ` [PATCH] Deprecate lm32 port Peter Maydell
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=a1dda44f-e521-ef82-f5bc-7435c81fe888@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=michael@walle.cc \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--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).