linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Arnd Bergmann <arnd@arndb.de>, Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arch <linux-arch@vger.kernel.org>,
	"moderated list:H8/300 ARCHITECTURE" 
	<uclinux-h8-devel@lists.sourceforge.jp>,
	"open list:TENSILICA XTENSA PORT (xtensa)" 
	<linux-xtensa@linux-xtensa.org>,
	Max Filippov <jcmvbkbc@gmail.com>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	linux-m68k <linux-m68k@lists.linux-m68k.org>,
	Greg Ungerer <gerg@linux-m68k.org>,
	Damien Le Moal <damien.lemoal@wdc.com>,
	linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [RFC PULL] remove arch/h8300
Date: Tue, 5 Apr 2022 08:32:35 +0900	[thread overview]
Message-ID: <ff20532f-7399-5fcb-d867-772a3e0fc8f1@opensource.wdc.com> (raw)
In-Reply-To: <CAK8P3a0QdFOJbM72geYTWOKumeKPSCVD8Nje5pBpZWazX0GEnQ@mail.gmail.com>

On 4/4/22 22:07, Arnd Bergmann wrote:
> On Sun, Apr 3, 2022 at 2:43 PM Christoph Hellwig <hch@infradead.org> wrote:
>>
>> On Tue, Mar 08, 2022 at 09:19:16AM +0100, Arnd Bergmann wrote:
>>> If there are no other objections, I'll just queue this up for 5.18 in
>>> the asm-generic
>>> tree along with the nds32 removal.
>>
>> So it is the last day of te merge window and arch/h8300 is till there.
>> And checking nw the removal has also not made it to linux-next.  Looks
>> like it is so stale that even the removal gets ignored :(
> 
> I was really hoping that someone else would at least comment.
> I've queued it up now for 5.19.
> 
> Should we garbage-collect some of the other nommu platforms where
> we're here? Some of them are just as stale:
> 
> 1. xtensa nommu has does not compile in mainline and as far as I can
> tell never did
>    (there was https://github.com/jcmvbkbc/linux-xtensa/tree/xtensa-5.6-esp32,
> which
>    worked at some point, but I don't think there was enough interest
> to get in merged)
> 
> 2. arch/sh Hitachi/Renesas sh2 (non-j2) support appears to be in a similar state
>     to h8300, I don't think anyone would miss it
> 
> 8<----- This may we where we want to draw the line ----
> 
> 3. arch/sh j2 support was added in 2016 and doesn't see a lot of
> changes, but I think
>     Rich still cares about it and wants to add J32 support (with MMU)
> in the future
> 
> 4. m68k Dragonball, Coldfire v2 and Coldfire v3 are just as obsolete as SH2 as
>    hardware is concerned, but Greg Ungerer keeps maintaining it, along with the
>    newer Coldfire v4 (with MMU)
> 
> 5. K210 was added in 2020. I assume you still want to keep it.

Still working on this one, I would like to keep it.

> 
> 7. Arm32 has several Cortex-M based platforms that are mainly kept for
>     legacy users (in particular stm32) or educational value.
> 
> 
>        Arnd
> 
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv


-- 
Damien Le Moal
Western Digital Research

  parent reply	other threads:[~2022-04-04 23:32 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08  6:52 [RFC PULL] remove arch/h8300 Christoph Hellwig
2022-03-08  8:19 ` Arnd Bergmann
2022-04-03 12:43   ` Christoph Hellwig
2022-04-04 13:07     ` Arnd Bergmann
2022-04-04 13:09       ` John Paul Adrian Glaubitz
2022-04-04 13:22       ` Geert Uytterhoeven
2022-04-04 23:34         ` Damien Le Moal
2022-04-06 21:25         ` Rob Landley
2022-04-07  7:17           ` Arnd Bergmann
2022-04-07  7:47             ` John Paul Adrian Glaubitz
2022-04-07  7:52               ` Christoph Hellwig
2022-04-07  8:34               ` Finn Thain
2022-04-04 13:41       ` Greg Ungerer
2022-04-05  3:23         ` Daniel Palmer
2022-04-05 13:07           ` Greg Ungerer
2022-04-09  0:24             ` Rob Landley
2022-04-09  1:59               ` Finn Thain
2022-04-09  4:18                 ` Greg Ungerer
2022-04-10  7:26                   ` Rob Landley
2022-04-10  8:08                     ` Rob Landley
2022-04-14  0:49                     ` Greg Ungerer
2022-04-09  3:37               ` Daniel Palmer
2022-04-10  7:13                 ` Rob Landley
2022-04-09  4:14               ` Greg Ungerer
2022-04-04 17:57       ` Max Filippov
2022-04-04 19:01         ` Arnd Bergmann
2022-04-04 19:14           ` Max Filippov
2022-04-04 19:35             ` Arnd Bergmann
2022-04-04 19:44               ` Arnd Bergmann
2022-04-04 20:56                 ` Max Filippov
2022-04-04 20:48               ` Max Filippov
2022-04-04 23:32       ` Damien Le Moal [this message]
2022-04-05 21:26       ` Guenter Roeck
2022-04-05 22:01         ` Arnd Bergmann
2022-04-06  0:12           ` Guenter Roeck
2022-05-06 14:07 ` Geert Uytterhoeven

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=ff20532f-7399-5fcb-d867-772a3e0fc8f1@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --cc=arnd@arndb.de \
    --cc=damien.lemoal@wdc.com \
    --cc=gerg@linux-m68k.org \
    --cc=hch@infradead.org \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=torvalds@linux-foundation.org \
    --cc=uclinux-h8-devel@lists.sourceforge.jp \
    --cc=ysato@users.sourceforge.jp \
    /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).