From: george anzinger <george@mvista.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] Making it easy to add system calls
Date: Wed, 05 Mar 2003 23:11:54 -0800 [thread overview]
Message-ID: <3E66F4BA.3000904@mvista.com> (raw)
In-Reply-To: <3E66BF21.4010608@pobox.com>
Jeff Garzik wrote:
>
> Your patch makes it impossible to tell at an easy glance which syscall
> is which number. The current code makes it quite obvious which numbers
> are assigned to which syscalls, and which syscall numbers are available
> for use. We lose valuable information with this patch, even if it does
> wind up to be functionally equivalent.
Of course the numbers as well as comments on the inactive or unused
entries could be added, just as they are today. I had also considered
the possiblility of adding the system call proto type as a parameter
in the macro. This could lead to a rather complete one entry
description of the call.
Still, it seems to not be in favor, so I will let it drop.
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2003-03-06 7:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 1:28 [PATCH] Making it easy to add system calls george anzinger
2003-03-06 3:23 ` Jeff Garzik
2003-03-06 7:11 ` george anzinger [this message]
2003-03-06 3:29 ` Linus Torvalds
2003-03-06 5:07 ` george anzinger
2003-03-07 16:33 ` Jamie Lokier
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=3E66F4BA.3000904@mvista.com \
--to=george@mvista.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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