linux-kernel - Re: [2.6 patch] cleanup asm/setup.h userspace visibility

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: <Pine.LNX.4.62.0612031154220.20605@pademelon.sonytel.be>
Date:	Sun, 3 Dec 2006 11:56:40 +0100 (CET)
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Russell King <rmk+lkml@....linux.org.uk>
cc:	Adrian Bunk <bunk@...sta.de>,
	Linux/m68k <linux-m68k@...ts.linux-m68k.org>,
	Linux Kernel Development <linux-kernel@...r.kernel.org>
Subject: Re: [2.6 patch] cleanup asm/setup.h userspace visibility

On Sat, 2 Dec 2006, Russell King wrote:
> On Sat, Dec 02, 2006 at 06:55:39PM +0100, Adrian Bunk wrote:
> > This patch makes the contents of the userspace asm/setup.h header 
> > consistent on all architectures:
> > - export setup.h to userspace on all architectures
> > - export only COMMAND_LINE_SIZE to userspace
> 
> On ARM, all the ATAGs are exported to userspace because they are an API
> for boot loaders to use.  Everything down to the comment "Memory map
> description" should be exported.

Same for m68k: at least MACH_*, CPU*, MMU*, and FPU* are needed to compile
m68kboot.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
-
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/