public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Sergey Shtylyov <s.shtylyov@omp.ru>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Artur Rojek <contact@artur-rojek.eu>,
	Guenter Roeck <linux@roeck-us.net>, Rich Felker <dalias@libc.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	linux-sh@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] sh updates for v6.5
Date: Thu, 6 Jul 2023 08:16:49 -0700	[thread overview]
Message-ID: <ZKba4SLzjjhHgOEs@infradead.org> (raw)
In-Reply-To: <9a6b730fc6c8e70ff034e2e3665478ec31858c29.camel@physik.fu-berlin.de>

Hi John,

thanks for taking up the sh maintainership!

Any chance you could do an inventoy on which arch/sh/ platforms are
currently working and maintained and which are just bitrot?

sh still has a lot of platform specific code that feels іt is rotting,
but some of that might just have been due to the lack of active
maintainance.

Once platform that I'm particulary interested in is dreamcast, which has
a rather oddball block driver (gdrom) and some very odd interaction with
the dma-mapping code.


  parent reply	other threads:[~2023-07-06 15:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05 21:43 [GIT PULL] sh updates for v6.5 John Paul Adrian Glaubitz
2023-07-06  4:52 ` pr-tracker-bot
2023-07-06 14:01 ` Guenter Roeck
2023-07-06 14:04   ` John Paul Adrian Glaubitz
2023-07-06 15:08     ` Guenter Roeck
2023-07-06 15:19       ` John Paul Adrian Glaubitz
2023-07-06 15:16 ` Christoph Hellwig [this message]
2023-07-06 15:23   ` John Paul Adrian Glaubitz
2023-07-08 21:25     ` Sergey Shtylyov
2023-07-08 21:49       ` John Paul Adrian Glaubitz
2023-07-08 21:58         ` Artur Rojek

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=ZKba4SLzjjhHgOEs@infradead.org \
    --to=hch@infradead.org \
    --cc=contact@artur-rojek.eu \
    --cc=dalias@libc.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=masahiroy@kernel.org \
    --cc=s.shtylyov@omp.ru \
    --cc=torvalds@linux-foundation.org \
    --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