From: Jeff Garzik <jgarzik@pobox.com>
To: Matthew Wilcox <willy@debian.org>
Cc: netdev@oss.sgi.com
Subject: Re: netdev_ops retraction
Date: Wed, 30 Jul 2003 14:50:03 -0400 [thread overview]
Message-ID: <20030730185003.GA9253@gtf.org> (raw)
In-Reply-To: <20030730184416.GI22222@parcelfarce.linux.theplanet.co.uk>
On Wed, Jul 30, 2003 at 07:44:16PM +0100, Matthew Wilcox wrote:
> Never mind the additional pointer dereference in the code, this is just
> a horribly large data structure. Unless someone convinces me otherwise,
> I'm going to drop this idea and revert to doing ethtool_ops as a separate
> data structure. I think there's still scope for a netdev_ops patch,
> but it's of dubious value and more of a 2.7 project.
Definitely OK with me.
And I think this is probably the best route for the moment, especially.
Jeff
next prev parent reply other threads:[~2003-07-30 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 18:44 netdev_ops retraction Matthew Wilcox
2003-07-30 18:50 ` Jeff Garzik [this message]
2003-07-30 23:35 ` Arnaldo Carvalho de Melo
2003-07-30 23:41 ` David S. Miller
2003-07-31 11:12 ` Matthew Wilcox
2003-07-31 12:49 ` multiple unicast mac address (was Re: netdev_ops retraction) Rick Payne
2003-07-31 13:27 ` Lars Marowsky-Bree
2003-07-31 14:44 ` Jeff Garzik
2003-07-31 15:09 ` Rick Payne
2003-08-03 19:06 ` jamal
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=20030730185003.GA9253@gtf.org \
--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).