| 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: <200807151925.50432.elendil@planet.nl> Date: Tue, 15 Jul 2008 19:25:49 +0200 From: Frans Pop <elendil@...net.nl> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: david@...g.hm, jeff@...zik.org, arjan@...radead.org, akpm@...ux-foundation.org, dwmw2@...radead.org, alan@...rguk.ukuu.org.uk, linux-kernel@...r.kernel.org Subject: Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel, use it in more drivers. On Tuesday 15 July 2008, you wrote: > So I think the _infrastructure_ is important. But the extreme "you have > to split it off entirely" mindset is equally as stupid as the "you must > compile it into the module" mindset. Agreed. All I've wanted to say is that having the _option_ to continue to compile it into the module can simplify certain use cases, including my current use of the kernel's own deb-pkg target for private builds of the kernel for testing purposes. One thing I would dearly like to see is the ability to choose a different location for firmware for my own custom built kernels than the location used for firmware from official Debian kernel packages so that at least those two don't clash. Doesn't look like that is possible with current git head. -- 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