[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080624040844.GE22526@linux-sh.org>
Date: Tue, 24 Jun 2008 13:08:44 +0900
From: Paul Mundt <lethal@...ux-sh.org>
To: Adrian Bunk <bunk@...nel.org>
Cc: Roland McGrath <roland@...hat.com>, linux-kernel@...r.kernel.org,
rmk@....linux.org.uk, cooloney@...nel.org, dev-etrax@...s.com,
dhowells@...hat.com, gerg@...inux.org,
yasutake.koichi@...panasonic.com, linux-parisc@...r.kernel.org,
paulus@...ba.org, linuxppc-dev@...abs.org,
linux-sh@...r.kernel.org, chris@...kel.net,
linux-mips@...ux-mips.org, ysato@...rs.sourceforge.jp,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [2.6 patch] asm/ptrace.h userspace headers cleanup
On Mon, Jun 23, 2008 at 08:48:09PM +0300, Adrian Bunk wrote:
> This patch contains the following cleanups for the asm/ptrace.h
> userspace headers:
> - include/asm-generic/Kbuild.asm already lists ptrace.h, remove
> the superfluous listings in the Kbuild files of the following
> architectures:
> - cris
> - frv
> - powerpc
> - x86
> - don't expose function prototypes and macros to userspace:
> - arm
> - blackfin
> - cris
> - mn10300
> - parisc
> - remove #ifdef CONFIG_'s around #define's:
> - blackfin
> - m68knommu
> - sh: AFAIK __SH5__ should work in both kernel and userspace,
> no need to leak CONFIG_SUPERH64 to userspace
Yes, that's fine. We've generally avoided relying entirely on the gcc
builtin definitions due to the rampant stupidity surrounding
__SH4_NOFPU__, but it is true that __SH5__ is always defined at least.
Acked-by: Paul Mundt <lethal@...ux-sh.org>
--
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/
Powered by blists - more mailing lists