From: Matthew Wilcox <willy@debian.org>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: Matthew Wilcox <willy@debian.org>, netdev@oss.sgi.com
Subject: Re: [PATCH] netdev_ops
Date: Thu, 10 Jul 2003 12:21:49 +0100 [thread overview]
Message-ID: <20030710112149.GC1939@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <C6F5CF431189FA4CBAEC9E7DD5441E0102229133@orsmsx402.jf.intel.com>
On Thu, Jul 10, 2003 at 12:47:13AM -0700, Feldman, Scott wrote:
> Can we get a HAVE_NETDEV_OPS?
I'll seriously consider it ... once we have a better idea where this is
all going. I'm a big fan of having _shared_ compatibility code rather
than something in each driver. Obviously we'll want to share drivers
between 2.4 and 2.6.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-07-10 11:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 7:47 [PATCH] netdev_ops Feldman, Scott
2003-07-10 7:42 ` David S. Miller
2003-07-10 11:21 ` Matthew Wilcox [this message]
2003-07-10 13:06 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2003-07-10 8:18 Feldman, Scott
2003-07-10 20:37 ` David S. Miller
2003-07-11 0:53 ` 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=20030710112149.GC1939@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.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 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).