linux-kernel - Re: CRIS port status, was: [PATCH] dump_stack: convert generic dump

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]

Message-ID: <CAK8P3a3sij2SZCe5JRgFsTqLB1gQq71MT8BfYqN--Wsd15g9pg@mail.gmail.com>
Date:   Wed, 7 Mar 2018 17:05:43 +0100
From:   Arnd Bergmann <arnd@...db.de>
To:     Michal Simek <monstr@...str.eu>
Cc:     Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
        Petr Mladek <pmladek@...e.com>, Tejun Heo <tj@...nel.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Dave Young <dyoung@...hat.com>,
        Andi Kleen <ak@...ux.intel.com>,
        Greentime Hu <green.hu@...il.com>,
        Vincent Chen <deanbo422@...il.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        adi-buildroot-devel@...ts.sourceforge.net,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Jesper Nilsson <jesper@....nu>,
        Mikael Starvik <starvik@...s.com>, linux-cris-kernel@...s.com
Subject: Re: CRIS port status, was: [PATCH] dump_stack: convert generic
 dump_stack into a weak symbol

On Wed, Mar 7, 2018 at 4:01 PM, Michal Simek <monstr@...str.eu> wrote:
> On 7.3.2018 15:09, Arnd Bergmann wrote:
>> On Wed, Mar 7, 2018 at 2:40 PM, Sergey Senozhatsky
>> <sergey.senozhatsky@...il.com> wrote:

>> 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 ;-)
>
> It is not like that. I definitely have less time for Microblaze to
> develop new stuff but Microblaze HW is still regularly updated and new
> hw features are coming there and new versions are created. We are also
> updating and testing newer kernels and using latest kernel at Xilinx. It
> is definitely not in state that we should just remove it.
>
> There are still a lot of users which are happy with current state and
> there is no pressure to add new features like SMP/address extension/etc
> that's why there is no huge development in arch/microblaze.

Ok, glad to hear that, thanks a lot for the clarification.

       Arnd