From: Jeff Garzik <jgarzik@pobox.com>
To: Maillist netdev <netdev@oss.sgi.com>
Cc: davem@redhat.com
Subject: ethtool_features?
Date: Wed, 27 Aug 2003 18:22:35 -0400 [thread overview]
Message-ID: <3F4D2F2B.2090401@pobox.com> (raw)
Hum. Instead of adding all these _get_foo ops to test dev->features
bits, would anyone mind if I created a single _get_features() ethtool
sub-ioctl?
Given the current ethtool_ops code, its implementation would in fact be
completely transparent to low-level drivers. It need only be
implemented in net/core/ethtool.c, without even adding a new hook.
Jeff
next reply other threads:[~2003-08-27 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 22:22 Jeff Garzik [this message]
2003-08-28 6:52 ` ethtool_features? David S. Miller
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=3F4D2F2B.2090401@pobox.com \
--to=jgarzik@pobox.com \
--cc=davem@redhat.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 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.