From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Brad Hards <bhards@bigpond.net.au>
Cc: Kai Henningsen <kaih@khms.westfalen.de>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: of ethernet names (was [PATCH] Futex Asynchronous
Date: Mon, 10 Jun 2002 19:02:40 -0400 [thread overview]
Message-ID: <3D053010.9060409@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0206091130490.13751-100000@home.transmeta.com> <8QbwdDPmw-B@khms.westfalen.de> <3D051DAF.6020107@mandrakesoft.com> <200206110852.57442.bhards@bigpond.net.au>
Brad Hards wrote:
> On Tue, 11 Jun 2002 07:44, Jeff Garzik wrote:
>
>>Actually, networking is moving in the direction described --
>>yes, as Linus points out, we will need the magic ioctl stuff for back
>>compat.
>>But the main way to communicate with a net device is netlink, already a
>>chardev. ifconfig actually should be updated to use netlink.
>
> Is there any documentation on the netlink API, beyond UTSL(iproute)?
> Reference would be good, but a tutorial would be ideal.
I don't know of any... Alexey/DaveM/Jamal are probably the best people
to ask.
Jeff
next prev parent reply other threads:[~2002-06-10 23:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 18:22 of ethernet names (was [PATCH] Futex Asynchronous Dr. David Alan Gilbert
2002-06-09 18:33 ` Linus Torvalds
2002-06-10 20:53 ` Kai Henningsen
2002-06-10 21:44 ` Jeff Garzik
2002-06-10 22:52 ` Brad Hards
2002-06-10 23:02 ` Jeff Garzik [this message]
2002-06-10 23:46 ` David Ford
[not found] <0C01A29FBAE24448A792F5C68F5EA47D29DD32@nasdaq.ms.ensim.com>
2002-06-10 23:20 ` Paul Menage
2002-06-10 23:32 ` Brad Hards
2002-06-10 23:36 ` Randy.Dunlap
2002-06-11 0:11 ` Brad Hards
2002-06-11 2:25 ` Andi Kleen
2002-06-11 2:34 ` Brad Hards
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=3D053010.9060409@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=bhards@bigpond.net.au \
--cc=kaih@khms.westfalen.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.