From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Tim Hockin <thockin@hockin.org>
Cc: Abraham vd Merwe <abraham@2d3d.co.za>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: ethtool documentation
Date: Mon, 05 Aug 2002 15:16:59 -0400 [thread overview]
Message-ID: <3D4ECF2B.2070000@mandrakesoft.com> (raw)
In-Reply-To: 200208051906.g75J6d122986@www.hockin.org
Tim Hockin wrote:
>>>Is there a document describing the ethtool ioctl's which need to be
>>>implemented in each ethernet driver?
>>
>>
>>Unfortunately not. There is a distinct lack of network driver docs at
>>the moment... The best documentation is looking at source code of
>>drivers that implement the most ioctls.
>
>
>
> I've got a draft of a quick overview doc. I need to add docs for a few of
> the newer commands, still, and I want to get into the structs for each call
> in more detail, too. I want to re-examine a few of recent additions,
> before they become too ubiquitous - am I too late to pipe up for my own
> aesthetics?
Sure, comments are always welcome.
And if you're bored, IMO putting the docs into Documentation/DocBook is
preferred :)
next prev parent reply other threads:[~2002-08-05 19:13 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 11:46 ethtool documentation Abraham vd Merwe
2002-08-05 15:42 ` Jeff Garzik
2002-08-05 19:06 ` Tim Hockin
2002-08-05 19:16 ` Jeff Garzik [this message]
2002-08-05 19:30 ` Jonathan Lundell
2002-08-05 20:20 ` Jeff Garzik
2002-08-06 10:17 ` Abraham vd Merwe
2002-08-06 10:07 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2002-08-06 15:41 Randy.Dunlap
2002-08-06 19:24 ` Richard B. Johnson
2002-08-06 19:40 ` Chris Friesen
2002-08-06 19:44 ` Randy.Dunlap
2002-08-06 20:03 ` Richard B. Johnson
2002-08-06 20:04 ` Randy.Dunlap
2002-08-06 20:36 ` Ben Greear
2002-08-06 21:15 ` Tim Hockin
2002-08-07 1:42 ` Richard B. Johnson
2002-08-07 3:33 ` Tim Hockin
2002-08-06 21:58 ` Alan Cox
2002-08-06 20:42 ` Randy.Dunlap
2002-08-06 22:27 ` Alan Cox
2002-08-19 19:00 ` Mark H. Wood
2002-08-07 1:57 ` Richard B. Johnson
2002-08-07 11:47 ` Alan Cox
2002-08-07 2:54 ` Ryan Anderson
2002-08-07 5:32 ` Dax Kelson
2002-08-07 6:30 ` Jonathan Lundell
2002-08-07 11:47 ` Alan Cox
2002-08-08 1:07 ` Peter Samuelson
2002-08-07 11:18 ` Richard B. Johnson
2002-08-07 12:05 ` Abraham vd Merwe
2002-08-07 18:44 ` Bernd Eckenfels
2002-08-07 20:16 ` erik
2002-08-07 8:02 ` Abraham vd Merwe
2002-08-06 20:57 Leif Sawyer
2002-08-07 1:51 ` Richard B. Johnson
2002-08-07 10:53 ` Jamie Lokier
2002-08-07 18:16 Leif Sawyer
2002-08-08 9:18 Helge Hafting
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=3D4ECF2B.2070000@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=abraham@2d3d.co.za \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@hockin.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 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.