From: Jeff Garzik <jgarzik@pobox.com>
To: "David S. Miller" <davem@redhat.com>
Cc: scott.feldman@intel.com, willy@debian.org, netdev@oss.sgi.com
Subject: Re: [PATCH] netdev_ops
Date: Thu, 10 Jul 2003 20:53:00 -0400 [thread overview]
Message-ID: <3F0E0A6C.5000703@pobox.com> (raw)
In-Reply-To: <20030710.133737.41660806.davem@redhat.com>
David S. Miller wrote:
> From: "Feldman, Scott" <scott.feldman@intel.com>
> Date: Thu, 10 Jul 2003 01:18:50 -0700
>
> With HAVE_NETDEV_OPS, you're right, we're maintaining the wrapper
> code outside the kernel. But, it does leave the possibility of
> having a shared backwards compatibility code for multiple (all?)
> drivers for those stuck with supporting kernels without netdev_ops.
>
> And precisely I am showing you how all this backwards compat
> stuff is going to hurt you. You can never truly take advantage
> of things that eliminate duplicated code in all the drivers,
> and this netdev_ops case is a great example.
Actually there is a solution that IMO will make everybody happy. Lemme
finish writing up my comments to Matthew...
Jeff
next prev parent reply other threads:[~2003-07-11 0:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 8:18 [PATCH] netdev_ops Feldman, Scott
2003-07-10 20:37 ` David S. Miller
2003-07-11 0:53 ` Jeff Garzik [this message]
-- 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-08 16:30 Matthew Wilcox
2003-07-08 20:44 ` Ben Greear
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
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=3F0E0A6C.5000703@pobox.com \
--to=jgarzik@pobox.com \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.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 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.