linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: george anzinger <george@mvista.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 22:23:13 -0500	[thread overview]
Message-ID: <3E66BF21.4010608@pobox.com> (raw)
In-Reply-To: <3E66A44A.6000808@mvista.com>

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.

	Jeff





  reply	other threads:[~2003-03-06  3:13 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 [this message]
2003-03-06  7:11   ` george anzinger
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=3E66BF21.4010608@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=george@mvista.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;
as well as URLs for NNTP newsgroup(s).