linux-kernel - Re: [GIT PULL, v4] S+core architecture (arch/score) support

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] [day] [month] [year] [list]

Message-ID: <OF4CFE082A.22292F01-ON48257624.0024EFF9-48257624.0025CD0B@sunplusct.com>
Date:	Tue, 1 Sep 2009 14:45:28 +0800
From:	liqin.chen@...plusct.com
To:	Arnd Bergmann <arnd@...db.de>
Cc:	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org
Subject: Re: [GIT PULL, v4] S+core architecture (arch/score) support

Arnd Bergmann <arnd@...db.de> 写于 2009-08-31 17:56:33:

> On Monday 31 August 2009 07:48:33 liqin.chen@...plusct.com wrote:
> > Arnd Bergmann <arnd@...db.de> 写于 2009-08-27 22:00:37:
> 
> __NR_ipc definitely should not be defined, it is a multiplexer
> for other system calls that have their own number, e.g. msgctl
> and semop. Look at e.g. how parisc does it in glibc.
> 

Ok, we do it as parisc does

> 
> Do you have a patch against the glibc git tree for score so I can look
> at what needs to be done? None of the changes should be specific to
> score after all, ideally it should all work without any glibc changes,
> though I realize that we are not there yet.
> 

I will send the patch to you soon.

liqin