linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Michal Simek <monstr@monstr.eu>, Andi Kleen <ak@linux.intel.com>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	linux-cris-kernel@axis.com, Petr Mladek <pmladek@suse.com>,
	Peter Zijlstra <peterz@infradead.org>,
	adi-buildroot-devel@lists.sourceforge.net,
	Steven Rostedt <rostedt@goodmis.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jesper Nilsson <jesper@jni.nu>, Greentime Hu <green.hu@gmail.com>,
	Tejun Heo <tj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vincent Chen <deanbo422@gmail.com>,
	Dave Young <dyoung@redhat.com>
Subject: Re: CRIS port status, was: [PATCH] dump_stack: convert generic dump_stack into a weak symbol
Date: Thu, 8 Mar 2018 16:51:16 +0100	[thread overview]
Message-ID: <20180308155116.GW17177@axis.com> (raw)
In-Reply-To: <CAK8P3a1KE_0+vDC48-NzzW8eT1YZ8MZRun-1GeRMNg+o8dqZUg@mail.gmail.com>

On Wed, Mar 07, 2018 at 03:09:27PM +0100, Arnd Bergmann wrote:
> On Wed, Mar 7, 2018 at 2:40 PM, Sergey Senozhatsky
> <sergey.senozhatsky@gmail.com> wrote:
> > On (03/07/18 13:48), Arnd Bergmann wrote:
> > [..]
> >> >
> >> > I can easily stop building blackfin - and, if the intention is to
> >> > remove it, there is not much point in wasting resources building it any
> >> > anyway.
> >>
> >> Right. At the moment, the plan is to remove metag, score, unicore32,
> >> m32r, frv and blackfin. If you are building any more of those, you can
> >> stop that as well.
> >>
> >> The fate of tile and mn10300 is still open, but I suspect they won't
> >> last long either.
> >
> > That's a huge list.
> >
> > I heard that CRIS is having some problems as well:
> > https://lkml.org/lkml/2018/1/11/403
> 
> Interesting. I thought I looked at cris when I made the list and found that
> it was still (semi-)regularly updated, so I assumed it was still needed.

Yeah, I've tried to keep it chugging along, but as I mentioned
in that thread, time and working hardware are running low.

I've not heard of anyone using real CRIS-hardware with mainline
releases for a couple of years now (except me :-)

> Jesper/Mikael: If you are considering to drop the port, I think it
> would make sense to do it at the same time as the others, so feel
> free to send me a removal pull request for 4.17 that I'll merge with
> the other removal patches, or I can offer to remove it myself.

I'm having mixed feelings, but I think it's time for Linux to
drop the CRIS-port. I'll prepare some patches for you in the CRIS-tree.

> Obviously if your plans have changed in the meantime and you
> prefer to keep it for a while longer, just let me know and I'll document
> the state in the tag description for the arch removal for future reference.
> 
> If we remove cris, it's probably also appropriate to ask the question
> about microblaze: Michal, I know your work on microblaze linux has
> been winding down over the years as the user base shrinks (just
> like for all others above). Should we keep it for a few more years for
> the remaining users, or is it time to let go? I would guess we still
> have active users on modern kernels, but that's what I thought
> about cris as well ;-)
> 
>       Arnd

/^JN - Jesper Nilsson
-- 
               Jesper Nilsson -- jesper.nilsson@axis.com

  parent reply	other threads:[~2018-03-08 15:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07 14:09 CRIS port status, was: [PATCH] dump_stack: convert generic dump_stack into a weak symbol Arnd Bergmann
2018-03-07 15:01 ` Michal Simek
2018-03-07 16:05   ` Arnd Bergmann
2018-03-08 15:51 ` Jesper Nilsson [this message]
2018-03-11 11:05   ` [GIT PULL] CRIS: Drop support for the CRIS-port Jesper Nilsson
2018-03-11 12:26     ` Mikael Starvik
2018-03-11 14:13     ` Stephen Rothwell
2018-03-11 20:00       ` Jesper Nilsson
2018-03-11 23:12         ` Stephen Rothwell
2018-03-12 20:21     ` Arnd Bergmann
2018-03-13  9:26       ` Jesper Nilsson

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=20180308155116.GW17177@axis.com \
    --to=jesper.nilsson@axis.com \
    --cc=adi-buildroot-devel@lists.sourceforge.net \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=deanbo422@gmail.com \
    --cc=dyoung@redhat.com \
    --cc=green.hu@gmail.com \
    --cc=jesper@jni.nu \
    --cc=linux-cris-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monstr@monstr.eu \
    --cc=peterz@infradead.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tj@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).