From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>
Cc: Chen Gang <chengang@emindsoft.com.cn>, qemu-devel@nongnu.org
Subject: Re: [PATCH] Deprecate TileGX port
Date: Fri, 19 Jun 2020 18:05:28 +0200 [thread overview]
Message-ID: <b256be1e-285b-b303-261c-fc29c1554e86@redhat.com> (raw)
In-Reply-To: <20200619155157.GX700896@redhat.com>
On 6/19/20 5:51 PM, Daniel P. Berrangé wrote:
> On Fri, Jun 19, 2020 at 04:48:31PM +0100, Peter Maydell wrote:
>> Deprecate our TileGX target support:
>> * we have no active maintainer for it
>> * it has had essentially no contributions (other than tree-wide cleanups
>> and similar) since it was first added
>> * the Linux kernel dropped support in 2018, as has glibc
>>
>> Note the deprecation in the manual, but don't try to print a warning
>> when QEMU runs -- printing unsuppressable messages is more obtrusive
>> for linux-user mode than it would be for system-emulation mode, and
>> it doesn't seem worth trying to invent a new suppressible-error
>> system for linux-user just for this.
>
> Potentially we could turn it off by default in configure, so it
> requires an explicit --target-list to request it, but either way,
> I don't mind.
This is the approach I started 2 releases back... Having a
DEPRECATED_TARGET environment variable, you add your target
there and warnings are displayed. It resulted not that easy,
and 2 releases passed...
>
>>
>> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>> ---
>> We discussed dropping this target last year:
>> https://patchew.org/QEMU/20191012071210.13632-1-philmd@redhat.com/
>> and before that in 2018, when Chen told us he didn't have time
>> to work on tilegx any more:
>> https://lists.gnu.org/archive/html/qemu-devel/2018-03/msg03955.html
>> Given that tilegx is no longer in upstream Linux I think it makes sense
>> to finally deprecate-and-drop our linux-user support for it.
>>
>> docs/system/deprecated.rst | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
>
>
> Regards,
> Daniel
>
next prev parent reply other threads:[~2020-06-19 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 15:48 [PATCH] Deprecate TileGX port Peter Maydell
2020-06-19 15:51 ` Daniel P. Berrangé
2020-06-19 16:05 ` Philippe Mathieu-Daudé [this message]
2020-06-19 15:56 ` Philippe Mathieu-Daudé
2020-06-19 16:24 ` no-reply
2020-06-19 19:02 ` Thomas Huth
-- 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 TileGX port Peter Maydell
2020-10-12 15:42 ` BALATON Zoltan via
2020-10-12 15:44 ` 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=b256be1e-285b-b303-261c-fc29c1554e86@redhat.com \
--to=philmd@redhat.com \
--cc=berrange@redhat.com \
--cc=chengang@emindsoft.com.cn \
--cc=peter.maydell@linaro.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).