public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-kernel@vger.kernel.org
Cc: czankel@tensilica.com, chris@zankel.net
Subject: Re: xtensa-clean-up-system-call-list-and-interface.patch added to -mm tree
Date: Thu, 18 Aug 2005 13:37:34 +0200	[thread overview]
Message-ID: <200508181337.35277.arnd@arndb.de> (raw)
In-Reply-To: <200508171949.j7HJnltq005970@shell0.pdx.osdl.net>

On Middeweken 17 August 2005 21:52, akpm@osdl.org wrote:
> +#ifdef __KERNEL_SYSCALLS__
>  
> +#include <linux/compiler.h>
> +#include <linux/types.h>
> +#include <linux/syscalls.h>
> +
> +struct pt_regs;
> +struct sigaction;
> +asmlinkage long xtensa_execve(char *filenamei, char **argv, char **envp,
> +                             struct pt_regs *regs);
> +asmlinkage long xtensa_clone(unsigned long clone_flags, unsigned long newsp,
> +                            struct pt_regs *regs);
> +asmlinkage long xtensa_pipe(unsigned long *fildes);
> +asmlinkage long xtensa_ptrace(long request, long pid, long addr, long data);
> +asmlinkage long xtensa_rt_sigaction(int sig,
> +                                   const struct sigaction __user *act,
> +                                   struct sigaction __user *oact,
> +                                   size_t sigsetsize);
>  

These definitions should not be #ifdef __KERNEL_SYSCALLS__. That define
used to have a very different meaning, which is now deprecated.

I think it would be best to simply put all the above stuff into a new
asm/syscalls.h which is then included from arch/xtensa/kernel/syscalls.c.

	Arnd <><

           reply	other threads:[~2005-08-18 11:45 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200508171949.j7HJnltq005970@shell0.pdx.osdl.net>]

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=200508181337.35277.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=chris@zankel.net \
    --cc=czankel@tensilica.com \
    --cc=linux-kernel@vger.kernel.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