From: Christoph Hellwig <hch@infradead.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: David Howells <dhowells@redhat.com>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add a stub by which a module can bind to the AFS syscall
Date: Wed, 30 Apr 2003 15:55:07 +0100 [thread overview]
Message-ID: <20030430155507.A8897@infradead.org> (raw)
In-Reply-To: <20030430144638.GB25076@gtf.org>; from jgarzik@pobox.com on Wed, Apr 30, 2003 at 10:46:38AM -0400
On Wed, Apr 30, 2003 at 10:46:38AM -0400, Jeff Garzik wrote:
> It's better than the alternative, having OpenAFS patch the system
> call table itself... ;-)
That's already taken care of with David's first patch. There's no
reason we can't have an afsctlfs like the nfsctlfs. But anyway,
please list the prototypes and usages of the subcalls here, maybe
some of them are generally usefull.
This kind of "I need a stuff fr a random syscall multiplexer"
requests are silly. APIs need review or you'll get the syssgi syndrome
really soon..
next prev parent reply other threads:[~2003-04-30 14:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 13:44 [PATCH] add a stub by which a module can bind to the AFS syscall David Howells
2003-04-30 14:02 ` Christoph Hellwig
2003-04-30 14:46 ` Jeff Garzik
2003-04-30 14:55 ` Christoph Hellwig [this message]
2003-04-30 14:57 ` chas williams
2003-04-30 15:02 ` Christoph Hellwig
2003-04-30 15:13 ` chas williams
2003-04-30 15:27 ` Christoph Hellwig
2003-04-30 15:33 ` chas williams
2003-04-30 15:38 ` Christoph Hellwig
2003-04-30 15:50 ` Arjan van de Ven
2003-04-30 15:42 ` Anton Blanchard
2003-04-30 15:56 ` viro
2003-05-08 14:01 ` David Howells
2003-04-30 15:30 ` David Howells
2003-04-30 15:37 ` Christoph Hellwig
2003-04-30 18:07 ` Jan Harkes
2003-04-30 18:19 ` Trond Myklebust
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=20030430155507.A8897@infradead.org \
--to=hch@infradead.org \
--cc=dhowells@redhat.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