From: Arnd Bergmann <arnd@arndb.de>
To: David Howells <dhowells@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>, Simon Derr <simon.derr@bull.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Remove syscall declarations from linux/key.h
Date: Wed, 8 Sep 2004 13:23:40 +0200 [thread overview]
Message-ID: <200409081323.45105.arnd@arndb.de> (raw)
In-Reply-To: <1070.1094635831@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 398 bytes --]
On Mittwoch, 8. September 2004 11:30, David Howells wrote:
>
> The attached patch removes the syscall declarations from linux/key.h as
> they're not really necessary - only entry.S should be calling them.
Actually, you should put those declarations into include/linux/syscalls.h,
where all other declarations for system calls are located. The macros
should just be left out.
Arnd <><
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-08 11:24 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 9:08 2.6.9-rc1-mm4 Andrew Morton
2004-09-07 11:59 ` 2.6.9-rc1-mm4 Terje Kvernes
2004-09-07 14:24 ` 2.6.9-rc1-mm4 Kasper Sandberg
2004-09-07 14:32 ` 2.6.9-rc1-mm4 Terje Kvernes
2004-09-07 17:04 ` 2.6.9-rc1-mm4 Francois Romieu
2004-09-07 18:30 ` 2.6.9-rc1-mm4 Terje Kvernes
2004-09-07 12:05 ` 2.6.9-rc1-mm4 Terje Kvernes
2004-09-07 12:21 ` 2.6.9-rc1-mm4 Simon Derr
2004-09-08 8:47 ` 2.6.9-rc1-mm4 Andrew Morton
2004-09-08 8:54 ` 2.6.9-rc1-mm4 Simon Derr
2004-09-08 9:30 ` [PATCH] Remove syscall declarations from linux/key.h David Howells
2004-09-08 11:23 ` Arnd Bergmann [this message]
2004-09-08 9:37 ` 2.6.9-rc1-mm4 David Howells
2004-09-08 12:06 ` [PATCH] Move syscall declarations from linux/key.h David Howells
2004-09-08 12:17 ` [PATCH] Move syscall declarations from linux/key.h [try #2] David Howells
2004-09-07 14:31 ` 2.6.9-rc1-mm4 Norberto Bensa
2004-09-07 15:45 ` 2.6.9-rc1-mm4 Zwane Mwaikambo
2004-09-07 16:46 ` 2.6.9-rc1-mm4 Danny ter Haar
2004-09-07 22:12 ` Killer CacheFS [was Re: 2.6.9-rc1-mm4] J.A. Magallon
2004-09-07 18:43 ` [patch] 2.6.9-rc1-mm4: small LOCALVERSION help text corrections Adrian Bunk
2004-09-07 21:27 ` Sam Ravnborg
2004-09-07 19:42 ` Adrian Bunk
2004-09-07 23:26 ` Ian Wienand
2004-09-07 19:02 ` [patch] 2.6.9-rc1-mm4: Makefile: remove tabs from empty lines Adrian Bunk
2004-09-07 21:14 ` Sam Ravnborg
2004-09-07 19:40 ` Adrian Bunk
2004-09-08 5:51 ` Dmitry Torokhov
2004-09-08 8:17 ` Sam Ravnborg
2004-09-07 19:26 ` [patch] 2.6.9-rc1-mm4: atyfb_base.c gcc 2.95 compile error Adrian Bunk
2004-09-08 0:38 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-09-07 20:01 ` 2.6.9-rc1-mm4 Lorenzo Allegrucci
2004-09-07 20:23 ` 2.6.9-rc1-mm4 Nathan Bryant
2004-09-07 21:07 ` 2.6.9-rc1-mm4 Bjorn Helgaas
2004-09-08 8:15 ` 2.6.9-rc1-mm4 Lorenzo Allegrucci
2004-09-07 21:47 ` 2.6.9-rc1-mm4 (compile stats) John Cherry
2004-09-07 21:58 ` John Cherry
2004-09-08 13:00 ` 2.6.9-rc1-mm4 William Lee Irwin III
2004-09-08 13:10 ` 2.6.9-rc1-mm4 David Howells
2004-09-08 20:16 ` 2.6.9-rc1-mm4 Nathan Lynch
2004-09-09 2:01 ` 2.6.9-rc1-mm4 William Lee Irwin III
2004-09-09 2:30 ` 2.6.9-rc1-mm4 William Lee Irwin III
2004-09-09 18:04 ` 2.6.9-rc1-mm4 Pasi Savolainen
2004-09-09 19:33 ` 2.6.9-rc1-mm4 Pasi Savolainen
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=200409081323.45105.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@osdl.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simon.derr@bull.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox