public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-sh@vger.kernel.org, linux-arch@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [RFC] remove arch/sh?
Date: Tue, 25 Jun 2019 10:56:16 +0200	[thread overview]
Message-ID: <20190625085616.GA32399@lst.de> (raw)

Hi Linus and maintainers,

arch/sh seems pretty much unmaintained these days.  The last time I got
any reply to sh patches from the list maintainers, and the last maintainer
pull request was over a year ago, and even that has been rather sporadic.

In the meantime we've not really seen any updates for new kernel features
and code seems to be bitrotting.

             reply	other threads:[~2019-06-25  8:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25  8:56 Christoph Hellwig [this message]
2019-06-25  8:56 ` [RFC] remove arch/sh? Christoph Hellwig
2019-06-25  9:02 ` John Paul Adrian Glaubitz
2019-06-25  9:02   ` John Paul Adrian Glaubitz
2019-06-25 11:21   ` Adam Borowski
2019-06-25 11:21     ` Adam Borowski
2019-06-25 12:02     ` John Paul Adrian Glaubitz
2019-06-25 12:02       ` John Paul Adrian Glaubitz
2019-06-25 12:50       ` Arnd Bergmann
2019-06-25 12:50         ` Arnd Bergmann
2019-06-25 14:28         ` Rich Felker
2019-06-25 14:28           ` Rich Felker
2019-06-25 15:48           ` Arnd Bergmann
2019-06-25 15:48             ` Arnd Bergmann
2019-06-26 11:25             ` Yoshinori Sato
2019-06-26 11:25               ` Yoshinori Sato
2019-06-26 15:38               ` Rich Felker
2019-06-26 15:38                 ` Rich Felker
2019-06-26 15:56                 ` John Paul Adrian Glaubitz
2019-06-26 15:56                   ` John Paul Adrian Glaubitz
2019-07-05 13:51                 ` Yoshinori Sato
2019-07-05 13:51                   ` Yoshinori Sato
2019-07-05 14:04                   ` John Paul Adrian Glaubitz
2019-07-05 14:04                     ` John Paul Adrian Glaubitz
2019-07-05 15:14                   ` Rich Felker
2019-07-05 15:14                     ` Rich Felker
2019-06-25 14:21   ` Rich Felker
2019-06-25 14:21     ` Rich Felker
2019-06-25 14:23     ` Christoph Hellwig
2019-06-25 14:23       ` Christoph Hellwig
2019-06-25 14:29       ` Rich Felker
2019-06-25 14:29         ` Rich Felker
2019-06-25 14:31         ` John Paul Adrian Glaubitz
2019-06-25 14:31           ` John Paul Adrian Glaubitz

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=20190625085616.GA32399@lst.de \
    --to=hch@lst.de \
    --cc=arnd@arndb.de \
    --cc=dalias@libc.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --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