From: Adam Borowski <kilobyte@angband.pl>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>, Arnd Bergmann <arnd@arndb.de>,
linux-sh@vger.kernel.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] remove arch/sh?
Date: Tue, 25 Jun 2019 13:21:46 +0200 [thread overview]
Message-ID: <20190625112146.GA9580@angband.pl> (raw)
In-Reply-To: <ccfa78f3-35c2-1d26-98b5-b21a76b90e1e@physik.fu-berlin.de>
On Tue, Jun 25, 2019 at 11:02:36AM +0200, John Paul Adrian Glaubitz wrote:
> On 6/25/19 10:56 AM, Christoph Hellwig wrote:
> > 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.
>
> We're still using sh4 in Debian
I wouldn't call it "used": it has popcon of 1, and despite watching many
Debian channels, I don't recall hearing a word about sh4 in quite a while.
Hardware development is dead: we were promised modern silicon by j-core
after original patents expired, but after J2 nothing happened, there was
silence from their side, and now https://j-core.org is down.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Packager's rule #1: upstream _always_ screws something up. This
⢿⡄⠘⠷⠚⠋⠀ is true especially if you're packaging your own project.
⠈⠳⣄⠀⠀⠀⠀
WARNING: multiple messages have this Message-ID (diff)
From: Adam Borowski <kilobyte@angband.pl>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>, Arnd Bergmann <arnd@arndb.de>,
linux-sh@vger.kernel.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] remove arch/sh?
Date: Tue, 25 Jun 2019 11:21:46 +0000 [thread overview]
Message-ID: <20190625112146.GA9580@angband.pl> (raw)
In-Reply-To: <ccfa78f3-35c2-1d26-98b5-b21a76b90e1e@physik.fu-berlin.de>
On Tue, Jun 25, 2019 at 11:02:36AM +0200, John Paul Adrian Glaubitz wrote:
> On 6/25/19 10:56 AM, Christoph Hellwig wrote:
> > 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.
>
> We're still using sh4 in Debian
I wouldn't call it "used": it has popcon of 1, and despite watching many
Debian channels, I don't recall hearing a word about sh4 in quite a while.
Hardware development is dead: we were promised modern silicon by j-core
after original patents expired, but after J2 nothing happened, there was
silence from their side, and now https://j-core.org is down.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Packager's rule #1: upstream _always_ screws something up. This
⢿⡄⠘⠷⠚⠋⠀ is true especially if you're packaging your own project.
⠈⠳⣄⠀⠀⠀⠀
next prev parent reply other threads:[~2019-06-25 11:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 8:56 [RFC] remove arch/sh? Christoph Hellwig
2019-06-25 8:56 ` 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 [this message]
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=20190625112146.GA9580@angband.pl \
--to=kilobyte@angband.pl \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=hch@lst.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.