From: george anzinger <george@mvista.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH ] POSIX clocks & timers take 10 (NOT HIGH RES)
Date: Tue, 12 Nov 2002 00:03:40 -0800 [thread overview]
Message-ID: <3DD0B5DC.BE90D497@mvista.com> (raw)
In-Reply-To: Pine.LNX.4.33L2.0211111539030.23954-100000@dragon.pdx.osdl.net
"Randy.Dunlap" wrote:
>
> Hi George,
>
> I have a couple of small comments on the latest POSIX interface
> patch (take 10 -- NOT HIGH RES).
>
> 1. arch/i386/kernel/entry.S uses nr_syscalls and the patch
> removes NR_syscalls from include/asm-i386/sys.h, but
> user-mode-linux needs/uses NR_syscalls. However, I see why you
> removed it from sys.h: it's basically a dead file.
> And it looks like include/linux/sys.h shouldn't have that
> #define in it (should be per arch).
The best place for this define, if it is needed at all, is
in unistd.h. It seems really silly to have to modify so
many files to add a system call. If it were not so late in
the game, I would offer up a single file system call thing,
but after 260 calls, well, maybe I will even so, but AFTER
the freeze since it will not add any new features.
>
> 2. again in arch/i386/kernel/entry.S: the added syscall number
> /*comments*/ are off by 1.
Oops! Just a comment though :)
--
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:[~2002-11-12 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 0:10 [PATCH ] POSIX clocks & timers take 10 (NOT HIGH RES) Randy.Dunlap
2002-11-12 8:03 ` george anzinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-06 6:31 george anzinger
2002-11-06 6:44 ` Robert Love
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=3DD0B5DC.BE90D497@mvista.com \
--to=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
/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