linux-kernel - Re: Microblaze init port v4

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: <4863E70A.2060108@seznam.cz>
Date:	Thu, 26 Jun 2008 20:59:22 +0200
From:	Michal Simek <monstr@...nam.cz>
To:	Arnd Bergmann <arnd@...db.de>
CC:	linux-arch@...r.kernel.org, alan@...rguk.ukuu.org.uk,
	vapier.adi@...il.com, matthew@....cx,
	microblaze-uclinux@...e.uq.edu.au, linux-kernel@...r.kernel.org,
	drepper@...hat.com, linuxppc-dev@...abs.org, will.newton@...il.com,
	hpa@...or.com, John.Linn@...inx.com, john.williams@...alogix.com
Subject: Re: Microblaze init port v4

Hi Arnd,

> On Thursday 26 June 2008, monstr@...nam.cz wrote:
>> We have there still problem with syscalls and we don't have chance to 
>> fix it to stable version, this is not part which I can do yourself. 
>> Microblaze will be n + 1 platform which use some old syscalls. 
>> I hope you understand.
> 
> That still leaves the problem that a lot of your syscalls have bugs
> copied from other platforms. If you need to maintain backwards compatibility
> with your existing binaries, that's fine, but please fix the code you are
> adding.

This is for now. I'll remove when I will have new toolchain.

I saw an email from you about.

M
--
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/