From: Matthew Wilcox <matthew@wil.cx>
To: Jaswinder Singh <jaswinder@infradead.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
kernelnewbies <kernelnewbies@nl.linux.org>,
David Woodhouse <dwmw2@infradead.org>,
rth@twiddle.net, rmk@arm.linux.org.uk, hskinnemoen@atmel.com,
cooloney@kernel.org, starvik@axis.com, dhowells@redhat.com,
ysato@users.sourceforge.jp, tony.luck@intel.com,
takata@linux-m32r.org, geert@linux-m68k.org, ralf@linux-mips.org,
schwidefsky@de.ibm.com, lethal@linux-sh.org, chris@zankel.net
Subject: Re: [PATCH 0/22] Introducing asm/syscalls.h
Date: Mon, 21 Jul 2008 00:16:55 -0600 [thread overview]
Message-ID: <20080721061655.GE24246@parisc-linux.org> (raw)
In-Reply-To: <1216620434.2705.38.camel@jaswinder.satnam>
On Mon, Jul 21, 2008 at 11:37:14AM +0530, Jaswinder Singh wrote:
> ???linux/syscalls.h is Linux syscall interfaces (non-arch-specific)
>
> So asm/syscalls.h is ???Linux syscall interfaces (arch-specific)
That's how you see it.
> 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.
sys_fork() does seem to be the worst case scenario. I suspect there's
similar ones (clone?). I still think it's worth adding them all to
linux/syscalls.h.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-07-21 6:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 22:21 [PATCH 0/22] Introducing asm/syscalls.h Jaswinder Singh
2008-07-20 22:26 ` [PATCH 1/22] " Jaswinder Singh
2008-07-20 22:27 ` [PATCH 2/22] alpha: " Jaswinder Singh
2008-07-20 22:30 ` [PATCH 3/22] arm: " Jaswinder Singh
2008-07-20 23:20 ` [PATCH 4/22] avr32: " Jaswinder Singh
2008-07-20 23:21 ` [PATCH 5/22] blackfin: " Jaswinder Singh
2008-07-20 23:25 ` [PATCH 6/22] cris: " Jaswinder Singh
2008-07-20 23:31 ` [PATCH 7/22] frv: " Jaswinder Singh
2008-07-20 23:32 ` [PATCH 8/22] h8300: " Jaswinder Singh
2008-07-20 23:33 ` [PATCH 9/22] ia64: " Jaswinder Singh
2008-07-20 23:35 ` [PATCH 10/22] m32r: " Jaswinder Singh
2008-07-20 23:37 ` [PATCH 11/22] m68k: " Jaswinder Singh
2008-07-20 23:39 ` [PATCH 12/22] m68knommu: " Jaswinder Singh
2008-07-20 23:40 ` [PATCH 13/22] mips: " Jaswinder Singh
2008-07-20 23:42 ` [PATCH 14/22] mn10300: " Jaswinder Singh
2008-07-20 23:46 ` [PATCH 15/22] parisc: " Jaswinder Singh
2008-07-20 23:50 ` [PATCH 16/22] s390: " Jaswinder Singh
2008-07-20 23:52 ` [PATCH 17/22] sh: " Jaswinder Singh
2008-07-20 23:53 ` [PATCH 18/22] sparc: " Jaswinder Singh
2008-07-20 23:54 ` [PATCH 19/22] um: " Jaswinder Singh
2008-07-20 23:55 ` [PATCH 20/22] v850: " Jaswinder Singh
2008-07-20 23:58 ` [PATCH 21/22] x86: " Jaswinder Singh
2008-07-21 0:00 ` [PATCH 22/22] xtensa: " Jaswinder Singh
2008-07-21 0:19 ` [PATCH 9/22] ia64: " Matthew Wilcox
2008-07-21 5:19 ` Jaswinder Singh
2008-07-24 13:09 ` [PATCH 4/22] avr32: " Haavard Skinnemoen
2008-07-24 15:07 ` Jaswinder Singh
2008-07-24 16:49 ` Haavard Skinnemoen
2008-07-21 0:28 ` [PATCH 0/22] " Alexey Dobriyan
2008-07-21 5:45 ` Jaswinder Singh
2008-07-21 5:55 ` Matthew Wilcox
2008-07-21 6:07 ` Jaswinder Singh
2008-07-21 6:16 ` Matthew Wilcox [this message]
2008-07-21 6:59 ` Jaswinder Singh
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=20080721061655.GE24246@parisc-linux.org \
--to=matthew@wil.cx \
--cc=adobriyan@gmail.com \
--cc=chris@zankel.net \
--cc=cooloney@kernel.org \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=geert@linux-m68k.org \
--cc=hskinnemoen@atmel.com \
--cc=jaswinder@infradead.org \
--cc=kernelnewbies@nl.linux.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ralf@linux-mips.org \
--cc=rmk@arm.linux.org.uk \
--cc=rth@twiddle.net \
--cc=schwidefsky@de.ibm.com \
--cc=starvik@axis.com \
--cc=takata@linux-m32r.org \
--cc=tony.luck@intel.com \
--cc=ysato@users.sourceforge.jp \
/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