> Fair enough, but in arch/i386/kernel/process.c:
>
> asmlinkage int sys_fork(struct pt_regs regs)
> asmlinkage int sys_clone(struct pt_regs regs)
> asmlinkage int sys_vfork(struct pt_regs regs)
> asmlinkage int sys_execve(struct pt_regs regs)
> etc...
>
> Should these be fixed too (the i386 arch is referred to quite a lot)?
$ grep 'asmlinkage int sys_' arch/i386/kernel/*.c | wc -l
19
And what is this all about?
$ grep -A 2 'unused)' arch/i386/kernel/*.c | grep -B 2 regs
arch/i386/kernel/ioport.c:asmlinkage int sys_iopl(unsigned long unused)
arch/i386/kernel/ioport.c-{
arch/i386/kernel/ioport.c- volatile struct pt_regs * regs = (struct pt_regs *) &unused;
--
arch/i386/kernel/signal.c:asmlinkage int sys_sigreturn(unsigned long __unused)
arch/i386/kernel/signal.c-{
arch/i386/kernel/signal.c- struct pt_regs *regs = (struct pt_regs *) &__unused;
--
arch/i386/kernel/signal.c:asmlinkage int sys_rt_sigreturn(unsigned long __unused)
arch/i386/kernel/signal.c-{
arch/i386/kernel/signal.c- struct pt_regs *regs = (struct pt_regs *) &__unused;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/