lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 8 Mar 2018 16:51:16 +0100
From:   Jesper Nilsson <jesper.nilsson@...s.com>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Michal Simek <monstr@...str.eu>,
        Andi Kleen <ak@...ux.intel.com>,
        Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
        linux-cris-kernel@...s.com, Petr Mladek <pmladek@...e.com>,
        Peter Zijlstra <peterz@...radead.org>,
        adi-buildroot-devel@...ts.sourceforge.net,
        Steven Rostedt <rostedt@...dmis.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Jesper Nilsson <jesper@....nu>,
        Greentime Hu <green.hu@...il.com>, Tejun Heo <tj@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Vincent Chen <deanbo422@...il.com>,
        Dave Young <dyoung@...hat.com>
Subject: Re: CRIS port status, was: [PATCH] dump_stack: convert generic
 dump_stack into a weak symbol

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@...il.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@...s.com

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ