mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>, Christoph Hellwig <hch@infradead.org>
Cc: Max Filippov <jcmvbkbc@gmail.com>,
	linux-arch <linux-arch@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Richard Kuo <rkuo@codeaurora.org>,
	"open list:QUALCOMM HEXAGON..." <linux-hexagon@vger.kernel.org>,
	Chen Liqin <liqin.linux@gmail.com>,
	Lennox Wu <lennox.wu@gmail.com>,
	Guan Xuetao <gxt@mprc.pku.edu.cn>,
	Guenter Roeck <linux@roeck-us.net>,
	Al Viro <viro@zeniv.linux.org.uk>,
	James Hogan <jhogan@kernel.org>,
	"open list:METAG ARCHITECTURE" <linux-metag@vger.kernel.org>,
	Jonas Bonn <jonas@southpole.se>,
	Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
	Stafford Horne <shorne@gmail.com>,
	openrisc@lists.librecores.org,
	David Howells <dhowells@redhat.com>,
	metcalf@alum.mit.edu
Subject: Re: Removing architectures without upstream gcc support
Date: Wed, 28 Feb 2018 09:59:24 +0100	[thread overview]
Message-ID: <6357df10-c3bd-587f-69d1-efb1855aaf85@redhat.com> (raw)
In-Reply-To: <CAK8P3a2VMbAARCFuBjY7TMuAfGM_h4BU3PfQA2C_pUFT34UHAA@mail.gmail.com>

On 02/23/2018 12:37 PM, Arnd Bergmann wrote:
> That makes more sense, yes. I'm still unsure about this one though. Chris in
> fact made the suggestion to remove the architecture from both glibc and kernel
> as with his departure from Mellanox there is nobody left from to maintain it.
> 
> I suggested keeping it as 'Orphaned' for the time being, given that the port
> is still in a good shape, much better than many other ports.
> 
> The known customers that sold TileGX based appliances (Cisco, Brocade,
> Checkpoint, Mikrotik, ...) tend to have long support cycles, and there have
> been attempts at getting Debian, OpenWRT and Centos distro support
> at least a few years ago.

Note that there is tilegx-*-linux-gnu and tilepro-*-linux-gnu.  Only the 
latter was removed from glibc.

Thanks,
Florian

  reply	other threads:[~2018-02-28  8:59 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22 15:45 Arnd Bergmann
2018-02-22 16:02 ` Christoph Hellwig
2018-02-22 16:19   ` Arnd Bergmann
2018-02-22 17:14   ` Max Filippov
2018-02-22 18:04     ` Christoph Hellwig
2018-02-23 11:37       ` Arnd Bergmann
2018-02-28  8:59         ` Florian Weimer [this message]
2018-02-22 16:07 ` Lennox Wu
2018-02-22 16:28 ` James Hogan
2018-02-22 16:34   ` Arnd Bergmann
2018-02-22 19:17 ` Richard Kuo
2018-02-22 22:43   ` Arnd Bergmann
2018-02-23 17:15     ` Richard Kuo
2018-02-28  2:06     ` Richard Kuo
2018-02-28  8:37       ` Arnd Bergmann
2018-03-03  1:43         ` Richard Kuo
2018-02-22 23:48 ` Guenter Roeck
2018-02-23 10:32   ` Arnd Bergmann
2018-02-23 12:09     ` Andy Shevchenko
2018-02-23 12:20       ` Arnd Bergmann
2018-02-23 14:32     ` Guenter Roeck
2018-02-23 15:43     ` Alan Cox
2018-02-23 17:10       ` Guenter Roeck
2018-02-23 18:19         ` Al Viro
2018-02-23 19:32           ` James Bottomley
2018-02-23 21:34             ` Adam Borowski
2018-02-24  4:04               ` Guenter Roeck
2018-02-24 21:55             ` Guenter Roeck
2018-02-25 19:39           ` [OpenRISC] " Richard Henderson
2018-02-23 23:49         ` Greg Ungerer
2018-02-25 20:28         ` Alan Cox
2018-02-25 22:50           ` Pavel Machek
2018-02-24  0:15 ` Florian Fainelli
2018-02-26  8:26   ` Arnd Bergmann
2018-02-26 22:11     ` Eric W. Biederman
2018-02-25 15:43 ` [OpenRISC] " Philipp Wagner
2018-02-26  8:00   ` Arnd Bergmann
2018-02-26 12:10     ` Philipp Wagner
2018-02-26 15:24       ` whitequark
2018-03-09 14:00 ` Xuetao Guan
2018-03-09 14:18 Guan Xuetao
2018-03-09 14:33 ` Arnd Bergmann

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=6357df10-c3bd-587f-69d1-efb1855aaf85@redhat.com \
    --to=fweimer@redhat.com \
    --cc=arnd@arndb.de \
    --cc=dhowells@redhat.com \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=hch@infradead.org \
    --cc=jcmvbkbc@gmail.com \
    --cc=jhogan@kernel.org \
    --cc=jonas@southpole.se \
    --cc=lennox.wu@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-metag@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=liqin.linux@gmail.com \
    --cc=metcalf@alum.mit.edu \
    --cc=openrisc@lists.librecores.org \
    --cc=rkuo@codeaurora.org \
    --cc=shorne@gmail.com \
    --cc=stefan.kristiansson@saunalahti.fi \
    --cc=viro@zeniv.linux.org.uk \
    /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
all inboxes | Powered by JetHome®