linux-kernel - Re: [RFC] [PATCH] asm-generic/unistd.h: handle symbol prefixes in cond

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: <4F47AF62.10507@imgtec.com>
Date:	Fri, 24 Feb 2012 15:40:18 +0000
From:	James Hogan <james.hogan@...tec.com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	<linux-arch@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] [PATCH] asm-generic/unistd.h: handle symbol prefixes in
 cond_syscall

On 24/02/12 15:09, Arnd Bergmann wrote:
> On Friday 24 February 2012, James Hogan wrote:
>> I've been looking at your initial comments for other architecture
>> submissions and they've been very helpful, but if you do have any
>> arch/metag specific suggestions I'd certainly welcome them.
> 
> I've had only a brief look. In general I recommend doing whatever
> openrisc does, they are currently the best implementation we have.

Okay, thanks for the tip.

> In order to get the code merged, you will need to move probing
> of on-chip buses to device trees rather than hardcoding the
> platform devices, that is probably the largest amount of work
> that is still needed unless you've done that already in a later
> version.

Okay, this is something I've been looking at.

> Do you have a git tree or patch with the latest source code?
> the only copy I could find is a 2.6.37 kernel inside of a huge
> tarball.

Sorry, but unfortunately that's the latest released version of the
kernel and I can't publish anything more recent at the moment.

Thanks
James

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