From: Andrew Morton <akpm@osdl.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add syscalls.h
Date: Sun, 1 Feb 2004 22:43:44 -0800 [thread overview]
Message-ID: <20040201224344.43d1c37d.akpm@osdl.org> (raw)
In-Reply-To: <20040201222254.39bc5b39.rddunlap@osdl.org>
"Randy.Dunlap" <rddunlap@osdl.org> wrote:
>
> | Date: Tue, 27 Jan 2004 16:46:15 -0800
> | From: Andrew Morton <akpm@osdl.org>
> | Subject: Re: NGROUPS 2.6.2rc2
> |
> |
> [snip]
> | rant. We have soooo many syscalls declared in .c files. We had a bug due
> | to this a while back. Problem is, we have no anointed header in which to
> | place them. include/linux/syscalls.h would suit. And unistd.h for
> | arch-specific syscalls. But that's not appropriate to this patch.
>
>
> I am working on this. Is anyone else?
>
> I have parts 2.6.1-non-arch* ready for testing, I believe,
> except that it will likely require more changes/additions.
>
> I have begun on 2.6.1-arch* but still have a ways to go.
>
> Caveats:
> I have only patched 2.6.1. I will update patches for 2.6.2-rc-current.
> I have only tested by building allmodconfig on P4.
> Have not test-booted yet.
>
> Patch files for 2.6.1 are here:
Looks sane to me.
+ * syscalls.h - Linux syscall interfaces (non-arch-specific)
...
+#include <linux/aio_abi.h>
+#include <linux/sched.h>
+#include <linux/socket.h>
+#include <linux/sysctl.h>
+#include <linux/time.h>
+#include <linux/posix-timers.h>
+#include <linux/uio.h>
+
+#include <asm/signal.h>
+#include <asm/stat.h>
I'd be inclined to lose the includes and just add forward decls for
structs. Of course, you'll need the includes for typedefs.
+extern asmlinkage long sys_unlink(const char __user *pathname);
+extern asmlinkage long sys_chmod(const char __user *filename, mode_t mode);
+extern asmlinkage long sys_fchmod(unsigned int fd, mode_t mode);
Maybe lose the `extern' too. It's just a waste of space. I normally put
it in for consistency if the surrounding code is done that way, but for a
new header file, why bother?
next prev parent reply other threads:[~2004-02-02 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040130163547.2285457b.rddunlap@osdl.org>
2004-02-02 6:22 ` Randy.Dunlap
2004-02-02 6:43 ` Andrew Morton [this message]
2004-02-03 20:29 ` Matt Mackall
2004-02-03 20:40 ` Richard B. Johnson
2004-02-03 21:18 ` Randy.Dunlap
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=20040201224344.43d1c37d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
/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
all inboxes | Powered by JetHome®