[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47FE848D.6050700@nortel.com>
Date: Thu, 10 Apr 2008 15:20:13 -0600
From: "Chris Friesen" <cfriesen@...tel.com>
To: "Kok, Auke" <auke-jan.h.kok@...el.com>
CC: Matthew Wilcox <matthew@....cx>,
Grant Grundler <grundler@...isc-linux.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Krzysztof Halasa <khc@...waw.pl>,
Frans Pop <elendil@...net.nl>, Ingo Molnar <mingo@...e.hu>,
jeff@...zik.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, e1000-devel@...ts.sourceforge.net,
linux-pci@...ey.karlin.mff.cuni.cz, akpm@...ux-foundation.org,
davem@...emloft.net, jesse.brandeburg@...el.com,
john.ronciak@...el.com, bruce.w.allan@...el.com, greg@...ah.com,
arjan@...ux.intel.com, rjw@...k.pl
Subject: Re: [patch] e1000=y && e1000e=m regression fix
Kok, Auke wrote:
> We want to move users over to e1000e, because with 2.6.26 they must (or at one
> point in time anyway).
>
> I'm all for making the move easier, but I'm really against prolonging these hacks
> that make people just bump their noses later. If they hit the problem now instead
> of when 2.6.26 ships, then it's all for the better IMHO.
Obviously e1000e hasn't been out for long enough to become common
knowledge. (Both Ingo and Linus running into the problem is probably a
sign...)
Maybe it would make sense to have "e1000 implies setting e1000e to the
same as e1000" for a couple releases, so that word gets around a bit
more. Then you can remove the auto-select of e1000e and anyone that
hasn't updated by then will get bit.
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists