| 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
| ||
|
Message-ID: <20140921191919.GS14691@waldemar-brodkorb.de> Date: Sun, 21 Sep 2014 21:19:19 +0200 From: Waldemar Brodkorb <mail@...demar-brodkorb.de> To: Guenter Roeck <linux@...ck-us.net> Cc: Mikael Starvik <mikael.starvik@...s.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Waldemar Brodkorb <mail@...demar-brodkorb.de>, Jesper Nilsson <jespern@...s.com>, Mikael Starvik <starvik@...s.com>, linux-cris-kernel <linux-cris-kernel@...s.com> Subject: Re: [RFC PATCH 8/8] Revert "percpu: free percpu allocation info for uniprocessor system" Hi Guenter, Guenter Roeck wrote, > On 09/21/2014 10:23 AM, Mikael Starvik wrote: > >Thanks for all your work with CRIS! CRISv10 is alive but is currently used as small helper CPUs close to hardware blocks. > > > > You are welcome. Now it would be even better if we could get the upstream code to work > with qemu. Which leads to the questions - is CRISv32 alive, and is there a chance > to get there ? Also, if CRISv10 is alive, is there any interest or even benefit to > maintain it in the latest kernel ? Because if not, we might as well drop v10 support > to simplify kernel maintenance. Please do not drop crisv10 support. Don't kill my foxboard lx cluster ;) http://www.openadk.org/cris/cris1.jpg http://www.openadk.org/cris/cris2.jpg best regards, Waldemar -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists