From: Peter Samuelson <peter@cadcamlab.org>
To: Ivan Passos <lists@cyclades.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com
Subject: Re: [RFC-2] Configuring Synchronous Interfaces in Linux
Date: Tue, 5 Dec 2000 14:41:32 -0600 [thread overview]
Message-ID: <20001205144132.D6567@cadcamlab.org> (raw)
In-Reply-To: <E143Ebi-000500-00@the-village.bc.nu> <Pine.LNX.4.10.10012051118140.1713-100000@main.cyclades.com>
In-Reply-To: <Pine.LNX.4.10.10012051118140.1713-100000@main.cyclades.com>; from lists@cyclades.com on Tue, Dec 05, 2000 at 11:23:50AM -0800
[Ivan Passos]
> - One ioctl that passes a pointer to a known structure in
> ifr.ifr_data as its argument.
struct sync_params_ioctl_data {
int opcode;
union {......
Seems straightforward to me. Basically just ioctl numbers within ioctl
numbers.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-05 21:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-05 5:58 [RFC-2] Configuring Synchronous Interfaces in Linux Ivan Passos
2000-12-05 9:38 ` Francois Romieu
2000-12-05 19:17 ` Ivan Passos
2000-12-05 9:41 ` Alan Cox
2000-12-05 15:15 ` Greg Parrott
2000-12-05 19:23 ` Ivan Passos
2000-12-05 20:41 ` Peter Samuelson [this message]
2000-12-05 21:56 ` Alan Cox
2000-12-05 14:43 ` Matthew G. Marsh
2000-12-05 19:40 ` Ivan Passos
2000-12-05 15:18 ` Paul Fulghum
[not found] <Pine.LNX.4.30.0012051925330.6718-100000@pc24.sr.bham.ac.uk>
2000-12-05 19:46 ` Ivan Passos
-- strict thread matches above, loose matches on Subject: below --
2000-12-05 22:55 Stuart Lynne
2000-12-06 1:21 ` Alan Cox
2000-12-06 1:34 ` Dan Hollis
2000-12-06 1:55 ` Stuart Lynne
2000-12-07 0:14 ` Krzysztof Halasa
2000-12-07 14:09 ` Alan Cox
2000-12-07 14:12 ` Jeff Garzik
2000-12-07 14:40 ` Alan Cox
2001-03-19 16:28 ` Krzysztof Halasa
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=20001205144132.D6567@cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@cyclades.com \
--cc=netdev@oss.sgi.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