From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Jan Harkes <jaharkes@cs.cmu.edu>
Cc: viro@math.psu.edu, rgooch@ras.ucalgary.ca, matthew@wil.cx,
clausen@gnu.org, bcrl@redhat.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [RFD w/info-PATCH] device arguments from lookup, partio
Date: Tue, 22 May 2001 17:52:53 MET-1 [thread overview]
Message-ID: <3A5DF9F50CC@vcnet.vc.cvut.cz> (raw)
[trimmed cc list down a bit - my MUA does not allow for so long CC:]
On 22 May 01 at 9:33, Jan Harkes wrote:
>
> something like,
>
> ssize_t kioctl(int fd, int type, int cmd, void *inbuf, size_t inlen,
> void *outbuf, size_t outlen);
If we are inventing new API, then if we could have
ssize_t kioctl(int fd, int type, int cmd,
const struct iovec* riov, size_t riov_len,
const struct iovec* wiov, size_t wiov_len);
then I'm almost sure that it will save couple of passing pointer to pointer
in structure headaches - for sure it will in code I maintain (ncpfs).
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
reply other threads:[~2001-05-22 15:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3A5DF9F50CC@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=bcrl@redhat.com \
--cc=clausen@gnu.org \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=rgooch@ras.ucalgary.ca \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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