[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.00.0804111327200.3143@woody.linux-foundation.org>
Date: Fri, 11 Apr 2008 13:29:22 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Krzysztof Halasa <khc@...waw.pl>
cc: Matthew Wilcox <matthew@....cx>,
Christoph Hellwig <hch@...radead.org>,
"Kok, Auke" <auke-jan.h.kok@...el.com>,
Ingo Molnar <mingo@...e.hu>, Jeff Garzik <jeff@...zik.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
NetDev <netdev@...r.kernel.org>,
e1000-list <e1000-devel@...ts.sourceforge.net>,
linux-pci maillist <linux-pci@...ey.karlin.mff.cuni.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
"David S. Miller" <davem@...emloft.net>,
Jesse Brandeburg <jesse.brandeburg@...el.com>,
"Ronciak, John" <john.ronciak@...el.com>,
"Allan, Bruce W" <bruce.w.allan@...el.com>,
Greg KH <greg@...ah.com>,
Arjan van de Ven <arjan@...ux.intel.com>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [patch] e1000=y && e1000e=m regression fix
On Fri, 11 Apr 2008, Krzysztof Halasa wrote:
> Linus Torvalds <torvalds@...ux-foundation.org> writes:
>
> > Nobody wants to care deeply whether it's a PCI-E or PCI chip. In fact,
> > it's almost impossible to tell. Here, quickly, tell me which one mine is
> > (this is from /sbin/lspci):
> >
> > 00:19.0 Ethernet controller: Intel Corporation 82566DM Gigabit Network Connection (rev 02)
> >
> > and tell me how you knew..
>
> I guess PCIE. You already came across a similar problem.
>
> Have I won something? :-)
Nope. You apparently guessed just because I had told earlier about how the
E1000 changes screwed over my setup.
The fact is, people don't know. And they shouldn't care. If the E1000
driver worked before, we simply shouldn't break that from a configuration
standpoint.
Linus
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists