From: Chris Wedgwood <cw@f00f.org>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com, "David S. Miller" <davem@redhat.com>
Subject: Re: PATCH: ethtool MII helpers
Date: Fri, 22 Jun 2001 17:34:59 +1200 [thread overview]
Message-ID: <20010622173459.D2642@metastasis.f00f.org> (raw)
In-Reply-To: <3B23AFC3.71CE2FD2@mandrakesoft.com> <20010622171037.D2576@metastasis.f00f.org> <3B32D694.CACF46D0@mandrakesoft.com>
In-Reply-To: <3B32D694.CACF46D0@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Fri, Jun 22, 2001 at 01:24:36AM -0400
On Fri, Jun 22, 2001 at 01:24:36AM -0400, Jeff Garzik wrote:
Sure, and that's planned. Wanna send me a patch for it? :)
Possibly, but I wonder if this is a kernel-space problem or not. Why
not put all the smarts into userland for it?
It will definitely fall back on the MII ioctls if ethtool media
support for the desired command doesn't exist.
Well, that is more or less as much as needs to be done. That, and
some kind of super-set API to be defined for all new stuff, having
two slightly different APIs for the same things sucks.
--cw
next prev parent reply other threads:[~2001-06-22 5:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-10 17:34 PATCH: ethtool MII helpers Jeff Garzik
2001-06-11 5:59 ` Pekka Savola
2001-06-11 6:10 ` Keith Owens
2001-06-12 17:09 ` Bogdan Costescu
2001-06-12 17:40 ` Jeff Garzik
2001-06-12 18:40 ` PATCH: ethtool MII helpers (vers 2) Jeff Garzik
2001-06-13 15:29 ` PATCH: ethtool MII helpers Bogdan Costescu
2001-06-13 16:56 ` Donald Becker
2001-06-13 20:24 ` Jeff Garzik
2001-06-15 17:22 ` Bogdan Costescu
2001-06-22 5:10 ` Chris Wedgwood
2001-06-22 5:24 ` Jeff Garzik
2001-06-22 5:34 ` Chris Wedgwood [this message]
2001-06-22 5:58 ` Jeff Garzik
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=20010622173459.D2642@metastasis.f00f.org \
--to=cw@f00f.org \
--cc=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).