From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Thomas Huth" <thuth@redhat.com>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Greg Kurz" <groug@kaod.org>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
"Cédric Le Goater" <clg@kaod.org>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Laurent Vivier" <laurent@vivier.eu>
Subject: Re: [PATCH] linux-user: Remove the deprecated ppc64abi32 target
Date: Wed, 15 Dec 2021 11:39:06 +0000 [thread overview]
Message-ID: <878rwmgkpw.fsf@linaro.org> (raw)
In-Reply-To: <fb033cf6-ab9b-3f85-e95d-0093715de48f@amsat.org>
Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
> On 12/15/21 09:49, Thomas Huth wrote:
>> It's likely broken, and nobody cared for picking it up again
>> during the deprecation phase, so let's remove this now.
>>
>> Since this is the last entry in deprecated_targets_list, remove
>> the related code in the configure script, too.
>
> Can we keep that part to keep the gate open to deprecate more
> targets / features?
I'm agnostic about it because it is essentially dead code so can
silently bit-rot. We can always resurrect the code from CI later if we
need to but I suspect future deprecation should be handled in meson?
Acked-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
next prev parent reply other threads:[~2021-12-15 12:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 8:49 [PATCH] linux-user: Remove the deprecated ppc64abi32 target Thomas Huth
2021-12-15 11:17 ` Philippe Mathieu-Daudé
2021-12-15 11:25 ` Thomas Huth
2021-12-15 11:39 ` Alex Bennée [this message]
2021-12-15 12:14 ` Philippe Mathieu-Daudé
2021-12-15 16:52 ` Richard Henderson
2021-12-15 17:34 ` Cédric Le Goater
2021-12-20 16:01 ` Laurent Vivier
2022-01-06 10:50 ` Laurent Vivier
2022-01-06 14:27 ` Alex Bennée
2022-01-05 9:47 ` Alex Bennée
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=878rwmgkpw.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=f4bug@amsat.org \
--cc=groug@kaod.org \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.