From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Borowski Subject: Re: [RFC] remove arch/sh? Date: Tue, 25 Jun 2019 13:21:46 +0200 Message-ID: <20190625112146.GA9580@angband.pl> References: <20190625085616.GA32399@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: John Paul Adrian Glaubitz Cc: Christoph Hellwig , Linus Torvalds , Yoshinori Sato , Rich Felker , Arnd Bergmann , linux-sh@vger.kernel.org, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-arch.vger.kernel.org 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. ⠈⠳⣄⠀⠀⠀⠀ From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tartarus.angband.pl ([54.37.238.230]:50050 "EHLO tartarus.angband.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727138AbfFYLV4 (ORCPT ); Tue, 25 Jun 2019 07:21:56 -0400 Date: Tue, 25 Jun 2019 13:21:46 +0200 From: Adam Borowski Subject: Re: [RFC] remove arch/sh? Message-ID: <20190625112146.GA9580@angband.pl> References: <20190625085616.GA32399@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Sender: linux-arch-owner@vger.kernel.org List-ID: To: John Paul Adrian Glaubitz Cc: Christoph Hellwig , Linus Torvalds , Yoshinori Sato , Rich Felker , Arnd Bergmann , linux-sh@vger.kernel.org, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org Message-ID: <20190625112146.TbNZ_7jarefJX2xEqL7l0g73FmSQfApk2LuMYgkkDO8@z> 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. ⠈⠳⣄⠀⠀⠀⠀