From: Paul Mundt <lethal@linux-sh.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org, rmk@arm.linux.org.uk,
cooloney@kernel.org, dev-etrax@axis.com, dhowells@redhat.com,
gerg@uclinux.org, yasutake.koichi@jp.panasonic.com,
linux-parisc@vger.kernel.org, paulus@samba.org,
linuxppc-dev@ozlabs.org, linux-sh@vger.kernel.org,
chris@zankel.net, linux-mips@linux-mips.org,
ysato@users.sourceforge.jp,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [2.6 patch] asm/ptrace.h userspace headers cleanup
Date: Tue, 24 Jun 2008 13:08:44 +0900 [thread overview]
Message-ID: <20080624040844.GE22526@linux-sh.org> (raw)
In-Reply-To: <20080623174809.GE4756@cs181140183.pp.htv.fi>
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@linux-sh.org>
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org, rmk@arm.linux.org.uk,
cooloney@kernel.org, dev-etrax@axis.com, dhowells@redhat.com,
gerg@uclinux.org, yasutake.koichi@jp.panasonic.com,
linux-parisc@vger.kernel.org, paulus@samba.org,
linuxppc-dev@ozlabs.org, linux-sh@vger.kernel.org,
chris@zankel.net, linux-mips@linux-mips.org,
ysato@users.sourceforge.jp,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [2.6 patch] asm/ptrace.h userspace headers cleanup
Date: Tue, 24 Jun 2008 04:08:44 +0000 [thread overview]
Message-ID: <20080624040844.GE22526@linux-sh.org> (raw)
In-Reply-To: <20080623174809.GE4756@cs181140183.pp.htv.fi>
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@linux-sh.org>
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: chris@zankel.net, dev-etrax@axis.com, ysato@users.sourceforge.jp,
linux-parisc@vger.kernel.org, linux-sh@vger.kernel.org,
linux-mips@linux-mips.org, cooloney@kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
paulus@samba.org, Roland McGrath <roland@redhat.com>,
gerg@uclinux.org, Andrew Morton <akpm@linux-foundation.org>,
yasutake.koichi@jp.panasonic.com, rmk@arm.linux.org.uk
Subject: Re: [2.6 patch] asm/ptrace.h userspace headers cleanup
Date: Tue, 24 Jun 2008 13:08:44 +0900 [thread overview]
Message-ID: <20080624040844.GE22526@linux-sh.org> (raw)
In-Reply-To: <20080623174809.GE4756@cs181140183.pp.htv.fi>
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@linux-sh.org>
next prev parent reply other threads:[~2008-06-24 4:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 17:48 [2.6 patch] asm/ptrace.h userspace headers cleanup Adrian Bunk
2008-06-23 17:48 ` Adrian Bunk
2008-06-23 17:48 ` Adrian Bunk
2008-06-23 20:08 ` Roland McGrath
2008-06-23 20:08 ` Roland McGrath
2008-06-23 20:08 ` Roland McGrath
2008-06-24 0:15 ` Greg Ungerer
2008-06-24 0:15 ` Greg Ungerer
2008-06-24 0:15 ` Greg Ungerer
2008-06-24 4:08 ` Paul Mundt [this message]
2008-06-24 4:08 ` Paul Mundt
2008-06-24 4:08 ` Paul Mundt
2008-06-24 5:18 ` Grant Grundler
2008-06-24 5:18 ` Grant Grundler
2008-06-24 5:18 ` Grant Grundler
2008-06-24 8:15 ` Jesper Nilsson
2008-06-24 8:15 ` Jesper Nilsson
2008-06-24 8:15 ` Jesper Nilsson
2008-06-24 8:25 ` Chris Zankel
2008-06-24 8:25 ` Chris Zankel
2008-06-24 8:25 ` Chris Zankel
2008-06-24 10:23 ` David Howells
2008-06-24 10:23 ` David Howells
2008-06-24 10:23 ` David Howells
2008-06-24 22:17 ` Paul Mackerras
2008-06-24 22:17 ` Paul Mackerras
2008-06-24 22:17 ` Paul Mackerras
2008-06-25 7:46 ` Russell King
2008-06-25 7:46 ` Russell King
2008-06-25 7:46 ` Russell King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080624040844.GE22526@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=chris@zankel.net \
--cc=cooloney@kernel.org \
--cc=dev-etrax@axis.com \
--cc=dhowells@redhat.com \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=rmk@arm.linux.org.uk \
--cc=roland@redhat.com \
--cc=yasutake.koichi@jp.panasonic.com \
--cc=ysato@users.sourceforge.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.