[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1216620434.2705.38.camel@jaswinder.satnam>
Date: Mon, 21 Jul 2008 11:37:14 +0530
From: Jaswinder Singh <jaswinder@...radead.org>
To: Matthew Wilcox <matthew@....cx>
Cc: Alexey Dobriyan <adobriyan@...il.com>,
LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
kernelnewbies <kernelnewbies@...linux.org>,
David Woodhouse <dwmw2@...radead.org>, rth@...ddle.net,
rmk@....linux.org.uk, hskinnemoen@...el.com, cooloney@...nel.org,
starvik@...s.com, dhowells@...hat.com, ysato@...rs.sourceforge.jp,
tony.luck@...el.com, takata@...ux-m32r.org, geert@...ux-m68k.org,
ralf@...ux-mips.org, schwidefsky@...ibm.com, lethal@...ux-sh.org,
chris@...kel.net
Subject: Re: [PATCH 0/22] Introducing asm/syscalls.h
Hello Matthew,
On Sun, 2008-07-20 at 23:55 -0600, Matthew Wilcox wrote:
> I think it makes more sense to add them to linux/syscall.h, possibly
> with comments mentioning which architectures implement them.
>
> If there are architectures with different prototypes for the same
> syscall, using an ifdef CONFIG_(arch) is /better/ annotation that having
> them in different header files.
>
linux/syscalls.h is Linux syscall interfaces (non-arch-specific)
So asm/syscalls.h is Linux syscall interfaces (arch-specific)
And if we add all arch dependent syscalls.h in linux/syscalls then it
will be very complex and do not look nice, for example sys_fork is keep
on changing for many architecture.
Thank you,
Jaswinder Singh.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists