From: Derrick J Brashear <shadow@dementia.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH: AFS system call registration function (was Re: Two fixes for 2.4.19-pre5-ac3)
Date: Sun, 13 Oct 2002 21:58:00 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96L.1021013215608.5586C-100000@scully.trafford.dementia.org> (raw)
In-Reply-To: <Pine.LNX.3.96L.1021013214541.5586B-100000@scully.trafford.dementia.org>
On Sun, 13 Oct 2002, Derrick J Brashear wrote:
Actually:
> > And I'd suggest to use u32
> > instead of long for the interface, to simplify 32bit compatiblity.
>
> Ok.
The version we have now uses long, so... (read on)
> > Also, what exactly is this call doing? I seems to be yet another
> > multiplexer syscall and we already have more than enough of those.
>
> Who wants to share theirs with us? Note that it was already reserved for
> us (look at the comments in the sys call table diffs) and we've been using
> it for years.
we have people with deployed utilities which call the afs system call,
because, well, it's the AFS system call. it would be good to maintain
compatibility with those, which means we should
a) keep using the same system call if we can
b) if so, keep using "long".
next prev parent reply other threads:[~2002-10-14 1:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-12 21:58 PATCH: AFS system call registration function (was Re: Two fixes for 2.4.19-pre5-ac3) shadow
2002-10-13 13:11 ` Christoph Hellwig
2002-10-14 1:48 ` Derrick J Brashear
2002-10-14 1:58 ` Derrick J Brashear [this message]
2002-10-14 14:23 ` Christoph Hellwig
2002-10-14 14:31 ` Derrick J Brashear
2002-10-14 16:32 ` Christoph Hellwig
2002-10-14 18:02 ` Derrick J Brashear
2002-10-14 18:04 ` Christoph Hellwig
2002-10-14 18:16 ` Derrick J Brashear
2002-10-14 18:34 ` Alexander Viro
2002-10-14 19:04 ` Derrick J Brashear
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=Pine.LNX.3.96L.1021013215608.5586C-100000@scully.trafford.dementia.org \
--to=shadow@dementia.org \
--cc=hch@infradead.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).