| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <alpine.LFD.1.00.0804101225570.3143@woody.linux-foundation.org> Date: Thu, 10 Apr 2008 12:27:45 -0700 (PDT) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Grant Grundler <grundler@...isc-linux.org> cc: Krzysztof Halasa <khc@...waw.pl>, Frans Pop <elendil@...net.nl>, Ingo Molnar <mingo@...e.hu>, jeff@...zik.org, matthew@....cx, auke-jan.h.kok@...el.com, 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 (was: Re: [regression] e1000e broke e1000) On Thu, 10 Apr 2008, Grant Grundler wrote: > > If e1000e is not getting compiled, my understanding was the original e1000 > driver will claim whatever devices it historically has. Yes. And the patch to do so was done by yours truly, exactly because I hit this thing ;) But it only works when the e1000e driver isn't enabled at all, which is why the "e1000e=m" case ends up being different, and Ingo then hit that one. Linus -- 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