From: Jeff Garzik <jgarzik@pobox.com>
To: Matthew Wilcox <willy@debian.org>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] ethtool_ops rev 4
Date: Sat, 02 Aug 2003 18:34:46 -0400 [thread overview]
Message-ID: <3F2C3C86.6000202@pobox.com> (raw)
In-Reply-To: <20030802222145.GE22222@parcelfarce.linux.theplanet.co.uk>
Matthew Wilcox wrote:
> On Fri, Aug 01, 2003 at 12:25:36PM -0400, Jeff Garzik wrote:
>
>>On Fri, Aug 01, 2003 at 04:46:56PM +0100, Matthew Wilcox wrote:
>>
>>>On Fri, Aug 01, 2003 at 11:40:21AM -0400, Jeff Garzik wrote:
>>>
>>>>* need SET_ETHTOOL_OPS macro or HAVE_ETHTOOL_OPS test macro or similar
>>
>>It's standard netdevice.h practice, and, he didn't disagree w/ my
>>rebuttal.
>
>
> OK, now that the two of you thrashed out a design, here's my implementation:
>
> diff -u drivers/net/8139too.c drivers/net/8139too.c
> --- drivers/net/8139too.c 31 Jul 2003 17:09:52 -0000
> +++ drivers/net/8139too.c 2 Aug 2003 18:38:25 -0000
> @@ -973,7 +973,7 @@
> dev->do_ioctl = netdev_ioctl;
> dev->tx_timeout = rtl8139_tx_timeout;
> dev->watchdog_timeo = TX_TIMEOUT;
> - dev->ethtool_ops = &rtl8139_ethtool_ops;
> + set_ethtool_ops(dev, &rtl8139_ethtool_ops);
>
> /* note: the hardware is not capable of sg/csum/highdma, however
> * through the use of skb_copy_and_csum_dev we enable these
> diff -u drivers/net/tg3.c drivers/net/tg3.c
> --- drivers/net/tg3.c 31 Jul 2003 11:12:10 -0000
> +++ drivers/net/tg3.c 2 Aug 2003 18:37:54 -0000
> @@ -6724,11 +6724,11 @@
> dev->do_ioctl = tg3_ioctl;
> dev->tx_timeout = tg3_tx_timeout;
> dev->poll = tg3_poll;
> - dev->ethtool_ops = &tg3_ethtool_ops;
> dev->weight = 64;
> dev->watchdog_timeo = TG3_TX_TIMEOUT;
> dev->change_mtu = tg3_change_mtu;
> dev->irq = pdev->irq;
> + set_ethtool_ops(dev, &tg3_ethtool_ops);
>
> err = tg3_get_invariants(tp);
> if (err) {
> diff -u include/linux/netdevice.h include/linux/netdevice.h
> --- include/linux/netdevice.h 31 Jul 2003 13:06:23 -0000
> +++ include/linux/netdevice.h 2 Aug 2003 18:37:16 -0000
> @@ -477,6 +477,10 @@
> */
> #define SET_NETDEV_DEV(net, pdev) ((net)->class_dev.dev = (pdev))
>
> +static inline void set_ethtool_ops(struct net_device *dev, struct ethtool_ops *
> ops)
> +{
> + dev->ethtool_ops = ops;
> +}
It needs to be a macro for maximum flexibility.
Also, no need to convert in-kernel drivers over to using it... Let
driver authors use it or not as they choose.
Jeff
next prev parent reply other threads:[~2003-08-02 22:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 15:02 [PATCH] ethtool_ops rev 4 Matthew Wilcox
2003-08-01 15:40 ` Jeff Garzik
2003-08-01 15:46 ` Matthew Wilcox
2003-08-01 16:25 ` Jeff Garzik
2003-08-01 20:20 ` David S. Miller
2003-08-01 22:26 ` Jeff Garzik
2003-08-01 22:32 ` David S. Miller
2003-08-01 23:01 ` Jeff Garzik
2003-08-01 23:01 ` David S. Miller
2003-08-01 23:17 ` Jeff Garzik
2003-08-01 23:19 ` David S. Miller
2003-08-01 23:42 ` Jeff Garzik
2003-08-01 23:43 ` David S. Miller
2003-08-01 22:35 ` Jeff Garzik
2003-08-01 22:34 ` David S. Miller
2003-08-01 23:09 ` Jeff Garzik
2003-08-01 23:08 ` David S. Miller
2003-08-01 23:35 ` Jeff Garzik
2003-08-01 23:34 ` David S. Miller
2003-08-02 22:21 ` Matthew Wilcox
2003-08-02 22:34 ` Jeff Garzik [this message]
2003-08-03 0:27 ` Matthew Wilcox
2003-08-03 3:14 ` Jeff Garzik
2003-08-03 14:56 ` Matthew Wilcox
2003-08-03 17:09 ` Jeff Garzik
2003-08-05 14:32 ` Matthew Wilcox
2003-08-03 0:28 ` 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=3F2C3C86.6000202@pobox.com \
--to=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=willy@debian.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 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).