linux-kernel - Re: [patch] e1000=y && e1000e=m regression fix (was: Re: [regression] e1000e broke e1000)

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.1.00.0804091838330.3143@woody.linux-foundation.org>
Date:	Wed, 9 Apr 2008 18:40:24 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Krzysztof Halasa <khc@...waw.pl>
cc:	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, Krzysztof Halasa wrote:
> 
> Nope, udev with normal distro config will load e1000e just fine.

Not for us that don't compile modules at all, or only modules for the 
devices we actually have.

Which should be about 99% of all kernel developers, because otherwise 
you're just wasting your time.

I certainly want the configurations to be sane by default, because I'm not 
in the insane camp that has every single module and depend on udev picking 
the right one out.

			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/