From: Richard Henderson <richard.henderson@linaro.org>
To: Filip Vidojevic <Filip.Vidojevic@Syrmia.com>,
f4bug@amsat.org, qemu-devel@nongnu.org
Cc: aleksandar.rikalo@syrmia.com, chenhuacai@kernel.org,
aurelien@aurel32.net, paulburton@kernel.org
Subject: Re: [PATCH] Revert "target/mips: Deprecate nanoMIPS ISA"
Date: Tue, 6 Apr 2021 08:20:41 -0700 [thread overview]
Message-ID: <7809edb1-42b3-1a17-ee7e-6a756d05987e@linaro.org> (raw)
In-Reply-To: <20210406132344.21476-1-Filip.Vidojevic@Syrmia.com>
On 4/6/21 6:23 AM, Filip Vidojevic wrote:
> NanoMIPS ISA is supported again, since mediaTek is taking over
> nanoMIPS toolchain development (confirmed at
> https://www.spinics.net/linux/fedora/libvir/msg217107.html).
>
> New release of the toolchain can be found at
> (https://github.com/MediaTek-Labs/nanomips-gnu-toolchain/releases/tag/nanoMIPS-2021.02-01).
>
> Reverting deprecation of nanoMIPS ISA requires following changes:
> MAINTAINERS: remove nanoMIPS ISA from orphaned ISAs
> deprecated.rst: remove nanoMIPS ISA from deprecated ISAs
>
> Signed-off-by: Filip Vidojevic<Filip.Vidojevic@Syrmia.com>
> ---
> MAINTAINERS | 4 -
> docs/system/deprecated.rst | 251 ++++++++++++++++++++++++++++++++++---
> 2 files changed, 235 insertions(+), 20 deletions(-)
I think we should retain the deprecation until you actually follow through with
any of the upstreaming.
You didn't even bother to commit your changes to a code repository -- merely
uploaded tarballs. There have been no posts to the gcc mailing lists about
nanomips.
A mere code dump is not active development.
r~
next prev parent reply other threads:[~2021-04-06 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 13:23 [PATCH] Revert "target/mips: Deprecate nanoMIPS ISA" Filip Vidojevic
2021-04-06 15:20 ` Richard Henderson [this message]
2021-04-06 15:46 ` 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=7809edb1-42b3-1a17-ee7e-6a756d05987e@linaro.org \
--to=richard.henderson@linaro.org \
--cc=Filip.Vidojevic@Syrmia.com \
--cc=aleksandar.rikalo@syrmia.com \
--cc=aurelien@aurel32.net \
--cc=chenhuacai@kernel.org \
--cc=f4bug@amsat.org \
--cc=paulburton@kernel.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).