From: Keith Owens <kaos@melbourne.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] XFS / IA64 system call conflict
Date: Tue, 24 Jul 2001 00:16:44 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005880@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005867@msgid-missing>
On Mon, 23 Jul 2001 09:49:49 -0700,
David Mosberger <davidm@hpl.hp.com> wrote:
>>>>>> On Tue, 24 Jul 2001 00:16:18 +1000, Keith Owens <kaos@melbourne.sgi.com> said:
>
> Keith> The problem is that IA64 is stuck on kernel 2.4.5 while XFS
> Keith> development is up to 2.4.7.
>
>Don't worry, a 2.4.7 based patch is in the works (and, no, I won't
>apologize for going on vacation...).
>
>What bothers me is that you apparently did not even try to contact me
>to get official numbers. At least, I don't see any earlier message
>from you in this regard.
There is no 'official' source for syscall numbers. The lack of a
standard process for assigning new syscall numbers is one of the
annoying things about the kernel and glibc. Everybody picks their own
on every arch, which almost guarantees conflicts.
next prev parent reply other threads:[~2001-07-24 0:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 13:53 [Linux-ia64] XFS / IA64 system call conflict Martin Wilck
2001-07-23 14:07 ` Nathan Straz
2001-07-23 14:09 ` Jes Sorensen
2001-07-23 14:16 ` Keith Owens
2001-07-23 14:24 ` Keith Owens
2001-07-23 16:49 ` David Mosberger
2001-07-23 18:51 ` David Mosberger
2001-07-24 0:16 ` Keith Owens [this message]
2001-07-24 0:19 ` David Mosberger
2001-07-24 0:30 ` Keith Owens
2001-07-24 0:35 ` David Mosberger
2001-07-24 1:04 ` Keith Owens
2001-07-25 15:45 ` Jes Sorensen
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=marc-linux-ia64-105590693005880@msgid-missing \
--to=kaos@melbourne.sgi.com \
--cc=linux-ia64@vger.kernel.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