linux-kernel - Re: [PATCH] Move most arches to asm-generic/current.h

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: <201204301638.29398.arnd@arndb.de>
Date:	Mon, 30 Apr 2012 16:38:29 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Stephen Boyd <sboyd@...eaurora.org>
Cc:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: [PATCH] Move most arches to asm-generic/current.h

On Monday 30 April 2012, Stephen Boyd wrote:
> I admit I haven't compile tested this on all the affected architectures.
> Looking at the architectures that are migrated here I don't see any that
> are defining get_current() as a macro except for alpha. Should I drop
> alpha from the patch? Or would it be easier if someone threw this into
> linux-next and see if it blows up?
> 
> In the meantime I can scrounge around for those kernel.org
> cross-compilers and see if I can compile alpha.

I'd say either get an Ack from the Alpha maintainers or drop that
hunk from your patch.

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