From: Roland Dreier <rdreier@cisco.com>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: Mark McLoughlin <markmc@redhat.com>,
Jeff Garzik <jeff@garzik.org>,
e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
"Ronciak, John" <john.ronciak@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Jason Lunz <lunz@reflexsecurity.com>
Subject: Re: RFR: New e1000 driver (e1000new), was: Re: e1000: backport ich9 support from 7.5.5 ?
Date: Fri, 29 Jun 2007 20:32:34 -0700 [thread overview]
Message-ID: <ada8xa29kx9.fsf@cisco.com> (raw)
In-Reply-To: <468594B7.6070309@intel.com> (Auke Kok's message of "Fri, 29 Jun 2007 16:24:39 -0700")
one possibility would be to merge e1000new with support only for chips
not supported by e1000, and semi-freeze e1000 (fixes only, new device
support goes into e1000new). Then if there are some devices that are
more naturally supported by e1000new, we could later on merge patches
to move support for those devices from e1000 to e1000new. Presumably
this would simplify e1000, since it would have to support a smaller
set of older devices. e1000new would stay relatively clean too since
it wouldn't have to handle anything too old.
And at every stage of the process, any given NIC would have only one
driver in the tree.
- R.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-06-30 3:32 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 17:29 e1000: backport ich9 support from 7.5.5 ? Mark McLoughlin
2007-06-29 17:50 ` Jason Lunz
2007-06-29 19:51 ` Kok, Auke
2007-06-29 20:22 ` Jason Lunz
2007-06-29 20:59 ` Jeff Garzik
2007-06-30 21:24 ` Mark McLoughlin
2007-07-02 23:52 ` Williams, Mitch A
2007-07-03 0:10 ` Rick Jones
2007-07-03 0:55 ` Jason Lunz
2007-07-03 1:44 ` Kok, Auke
2007-07-03 7:15 ` Christoph Hellwig
2007-07-03 13:13 ` [E1000-devel] " Jeff Garzik
2007-06-29 20:55 ` Jeff Garzik
2007-06-29 21:39 ` Kok, Auke
2007-06-29 22:03 ` Andrew Morton
2007-06-29 22:11 ` Jeff Garzik
2007-06-29 23:24 ` RFR: New e1000 driver (e1000new), was: " Kok, Auke
2007-06-29 23:38 ` Arjan van de Ven
2007-07-08 18:20 ` Jeff Garzik
2007-07-08 20:14 ` Arjan van de Ven
2007-07-08 22:01 ` [E1000-devel] " Jonathan Lundell
2007-06-30 3:32 ` Roland Dreier [this message]
2007-07-08 18:20 ` Jeff Garzik
2007-07-06 19:07 ` Jeff Garzik
2007-07-07 0:13 ` Kok, Auke
2007-07-07 12:23 ` James Chapman
2007-07-08 18:41 ` James Chapman
2007-07-07 18:59 ` Andrew Grover
2007-06-29 23:57 ` Andrew Grover
2007-06-30 0:02 ` Andrew Grover
2007-06-30 0:09 ` Jeff Garzik
2007-06-30 1:29 ` Jim McCullough
2007-06-30 1:31 ` Jim McCullough
2007-06-30 2:34 ` [E1000-devel] " Kok, Auke
2007-06-30 2:31 ` Kok, Auke
2007-06-30 8:25 ` Christoph Hellwig
2007-07-03 22:48 ` Splitting e1000 (Was: Re: e1000: backport ich9 support from 7.5.5 ?) Kok, Auke
2007-07-05 18:32 ` Kok, Auke
2007-07-06 0:22 ` Jeff Garzik
2007-07-07 0:14 ` Kok, Auke
2007-07-07 13:58 ` James Chapman
2007-07-07 19:04 ` Francois Romieu
2007-07-07 21:54 ` Kok, Auke
2007-07-08 1:32 ` Stephen Hemminger
2007-07-08 10:07 ` James Chapman
2007-07-08 16:29 ` Arjan van de Ven
2007-07-08 18:06 ` Jeff Garzik
2007-07-08 19:24 ` Andrew Grover
2007-07-09 17:56 ` Jeff Garzik
2007-07-08 20:05 ` Arjan van de Ven
2007-07-09 18:39 ` Jeff Garzik
2007-07-09 18:46 ` Stephen Hemminger
2007-07-09 19:36 ` Arjan van de Ven
2007-07-09 20:46 ` Kok, Auke
2007-07-09 22:26 ` Jeff Garzik
2007-07-13 21:45 ` Kok, Auke
2007-07-13 22:08 ` Jeff Garzik
2007-07-13 22:13 ` Kok, Auke
2007-07-08 18:08 ` Jeff Garzik
2007-07-08 17:41 ` Jeff Garzik
2007-06-30 14:31 ` e1000: backport ich9 support from 7.5.5 ? James Chapman
2007-06-30 16:29 ` Kok, Auke
2007-07-01 10:45 ` James Chapman
2007-06-30 8:26 ` Christoph Hellwig
2007-06-29 22:16 ` Kok, Auke
2007-06-29 22:07 ` Jeff Garzik
2007-06-29 21:39 ` Andy Gospodarek
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=ada8xa29kx9.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=auke-jan.h.kok@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeff@garzik.org \
--cc=john.ronciak@intel.com \
--cc=lunz@reflexsecurity.com \
--cc=markmc@redhat.com \
--cc=netdev@vger.kernel.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).