From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Jeff Garzik <jeff@garzik.org>, Andrew Morton <akpm@osdl.org>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Lennert Buytenhek <buytenh@wantstofly.org>,
David Acker <dacker@roinet.com>,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Netdev List <netdev@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: [RFT] e100 driver on ARM
Date: Thu, 26 Apr 2007 09:20:36 -0700 [thread overview]
Message-ID: <4630D154.7050708@intel.com> (raw)
In-Reply-To: <4630CEA9.6050100@garzik.org>
Jeff Garzik wrote:
> Kok, Auke wrote:
>> Jeff, I think I should just push the IO patch and the sbit code to
>> Andrew and have it sit there. That is a vastly larger test resource than
>> we currently can generate for this. If needed we just let is sit there
>> for a whole release cycle before moving it to #upstream.
>
> The sbit code has been in -mm via netdev-2.6.git#ALL for many months
> now. I am certainly open to adding any number of "for -mm only" style
> patches that you wish to pass along, for /any/ driver: e100, e1000, ixgb.
I think we should then just bite the bullet and move it over to #upstream for
2.6.22, that gives us another full release cycle to monitor it.
I'll post 2 patches in a second. the first is for upstream and allows the driver
to run with an invalid mac address in case the user overrides the eeprom
checksum (in which case the mac address could likely be wrong). The second one
is the I/O mode patch and for Andrew (MM), allthough the I/O mode is disabled by
default, so it should be safe to put in upstream as well, but I leave that up to
you to decide.
Auke
next prev parent reply other threads:[~2007-04-26 16:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 10:39 [RFT] e100 driver on ARM Jeff Garzik
2006-09-04 12:31 ` Lennert Buytenhek
2007-03-28 23:04 ` Kok, Auke
2007-03-29 5:17 ` David Acker
2007-03-29 14:10 ` Lennart Sorensen
2007-04-16 15:07 ` David Acker
2007-04-17 17:35 ` Lennart Sorensen
2007-04-26 13:41 ` David Acker
2007-04-26 13:50 ` Lennert Buytenhek
2007-04-26 15:12 ` Jeff Garzik
2007-04-26 15:40 ` Kok, Auke
2007-04-26 16:09 ` Jeff Garzik
2007-04-26 16:20 ` Kok, Auke [this message]
2007-04-26 16:19 ` H. Peter Anvin
2007-04-27 19:01 ` Lennart Sorensen
2006-09-04 14:34 ` Catalin Marinas
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=4630D154.7050708@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=akpm@osdl.org \
--cc=buytenh@wantstofly.org \
--cc=dacker@roinet.com \
--cc=jeff@garzik.org \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=netdev@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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).