netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Matthew Wilcox <willy@debian.org>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] netdev_ops
Date: Tue, 08 Jul 2003 13:44:32 -0700	[thread overview]
Message-ID: <3F0B2D30.4020102@candelatech.com> (raw)
In-Reply-To: <20030708163042.GL23597@parcelfarce.linux.theplanet.co.uk>

Matthew Wilcox wrote:
> After a conversation with acme, I realised that ethtool_ops is far too
> narrow scope.  What we need are netdev_ops.  This patch renames the
> ethtool_ops to netdev_ops and fixes some other minor flaws:
> 
>  - add _len() ops for operations which previously had to kmalloc their
>    own memory.
>  - move the netdev_ops from ethtool.h to netdevice.h
>  - makes some ops generic as requested by Jeff Garzik.
> 
> I think netdev_ops is still a little too ethtool-specific; something
> I'd like to do is convert the parameters to be a little less
> ethtool-related.  For example, instead of ->get_drvinfo, I'd like to
> see ethtool_get_drvinfo() call several methods and fill in all the data
> that way.
> 
> But let's see what everyone thinks of this patch first ...
> 

> + * Each operation is passed a &struct net_device as its first parameter.

Some of these are missing their netdevice arg?
> +	int	(*get_regs_len)(struct ethtool_regs *);

> +	int	(*self_test_len)(struct ethtool_test *);

> +	int	(*get_strings_len)(struct ethtool_gstrings *);

> +	int	(*get_stats_len)(struct ethtool_stats *);



-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear

  reply	other threads:[~2003-07-08 20:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-08 16:30 [PATCH] netdev_ops Matthew Wilcox
2003-07-08 20:44 ` Ben Greear [this message]
2003-07-08 21:25   ` Matthew Wilcox
2003-07-08 22:08     ` David S. Miller
2003-07-09 16:15       ` Matthew Wilcox
2003-07-09 17:11         ` Ben Greear
2003-07-09 17:25           ` Matthew Wilcox
2003-07-09 18:14           ` Jeff Garzik
2003-07-09 18:24             ` Ben Greear
2003-07-11 19:32         ` Jeff Garzik
2003-07-11 19:51           ` Ben Greear
2003-07-11 19:58             ` Jeff Garzik
2003-07-11 20:07               ` Ben Greear
2003-07-11 20:04           ` Matthew Wilcox
2003-07-14  5:53             ` Arnaldo Carvalho de Melo
  -- strict thread matches above, loose matches on Subject: below --
2003-07-10  7:47 Feldman, Scott
2003-07-10  7:42 ` David S. Miller
2003-07-10 11:21 ` Matthew Wilcox
2003-07-10 13:06   ` Jeff Garzik
2003-07-10  8:18 Feldman, Scott
2003-07-10 20:37 ` David S. Miller
2003-07-11  0:53   ` 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=3F0B2D30.4020102@candelatech.com \
    --to=greearb@candelatech.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).