qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: Chris Wulff <crwulff@gmail.com>, Marek Vasut <marex@denx.de>,
	devel@lists.libvirt.org,
	Sandra Loosemore <sandra@codesourcery.com>
Subject: Re: [PATCH-for-8.2] target/nios2: Deprecate the Nios II architecture
Date: Fri, 17 Nov 2023 09:46:37 +0100	[thread overview]
Message-ID: <fa514dc7-ffbd-4760-9df7-4536929c8b48@redhat.com> (raw)
In-Reply-To: <20231117070250.32932-1-philmd@linaro.org>

On 17/11/2023 08.02, Philippe Mathieu-Daudé wrote:
> See commit 9ba1caf510 ("MAINTAINERS: Mark the Nios II CPU as orphan"),
> last contribution from Chris was in 2012 [1] and Marek in 2018 [2].
> 
> [1] https://lore.kernel.org/qemu-devel/1352607539-10455-2-git-send-email-crwulff@gmail.com/
> [2] https://lore.kernel.org/qemu-devel/805fc7b5-03f0-56d4-abfd-ed010d4fa769@denx.de/
> 
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
>   docs/about/deprecated.rst | 15 +++++++++++++++
>   hw/nios2/10m50_devboard.c |  1 +
>   hw/nios2/generic_nommu.c  |  1 +
>   3 files changed, 17 insertions(+)

Being orphan for so long in QEMU, I guess it makes sense to mark it as 
deprecated here now. We can still reconsider if a new maintainer shows up...

Reviewed-by: Thomas Huth <thuth@redhat.com>



  reply	other threads:[~2023-11-17  8:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17  7:02 [PATCH-for-8.2] target/nios2: Deprecate the Nios II architecture Philippe Mathieu-Daudé
2023-11-17  8:46 ` Thomas Huth [this message]
2023-11-17 15:57   ` Sandra Loosemore
2023-11-17 16:35 ` Richard Henderson
2023-11-17 17:00 ` Marek Vasut
2023-11-17 17:33 ` 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=fa514dc7-ffbd-4760-9df7-4536929c8b48@redhat.com \
    --to=thuth@redhat.com \
    --cc=crwulff@gmail.com \
    --cc=devel@lists.libvirt.org \
    --cc=marex@denx.de \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sandra@codesourcery.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 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).