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
| ||
|
Date: Sat, 21 May 2016 09:31:48 -0700 From: Linus Torvalds <torvalds@...ux-foundation.org> To: William Breathitt Gray <vilhelm.gray@...il.com> Cc: Greg KH <gregkh@...uxfoundation.org>, Andrew Morton <akpm@...ux-foundation.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [GIT PULL] Driver core update for 4.7-rc1 On Sat, May 21, 2016 at 9:20 AM, William Breathitt Gray <vilhelm.gray@...il.com> wrote: > > I'll submit patches to resolve these warnings and errors. No. I will disable that ISA config option. We're not randomly making old drivers available on modern platforms. Really. We're not suddenly enabling ISA on x86-64 after having successfully gotten rid of that insane crap long long ago. If you have *specific* dribvers that are actually relevant for some reason, make those ones available based on other options. For example, we've had the ISA_DMA_API config option to say "we support a subset of ISA, even when we don't actually want to ever see actual plug-in ISA cards". Your patch already resulted in having to add several cases of - depends on ISA + depends on X86 && ISA because you tried to randomly widen what "ISA" meant. No. No no no. No more "let's randomly change what ISA is". Do this enabling one driver at a time, or not at all. I'm not at all interested in seeing some kind of generic "we will support random shit on modern platfoms" crap. 99% of all drivers that depend on ISA have no maintainership, and will never get any maintainership. Linus
Powered by blists - more mailing lists