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: Wed, 01 Aug 2012 11:21:59 +0200 From: Lars-Peter Clausen <lars@...afoo.de> To: Borislav Petkov <bp@...en8.de>, Thierry Reding <thierry.reding@...onic-design.de>, Steven Rostedt <rostedt@...dmis.org>, Dave Jones <davej@...hat.com>, Linux Kernel <linux-kernel@...r.kernel.org> Subject: Re: awful kconfig help texts. On 08/01/2012 10:56 AM, Borislav Petkov wrote: > On Wed, Aug 01, 2012 at 09:47:42AM +0200, Thierry Reding wrote: >> On Tue, Jul 31, 2012 at 07:42:49PM +0200, Borislav Petkov wrote: >>> On Tue, Jul 31, 2012 at 01:26:38PM -0400, Steven Rostedt wrote: >>>> Then shouldn't this not have a prompt and just be selected by those >>>> PWM drivers below? >>> >>> It gives an empty menu due to the deps of the single PWM drivers. >>> >>> But the whole CONFIG_PWM thing should simply depend on !X86 so that it >>> doesn't appear in drivers/. >> >> I don't think that's a good idea. That would mean I would have to add >> !SPARC and !S390 and many other to that list as well. Also there are a >> couple of drivers that are in the process of being ported which are not >> restricted to ARM or embedded in general. So even if we make this !X86 >> now, eventually it will pop up again. > > Hmm, how about having a synthetic define CONFIG_ARCH_PWM and each arch > which has such a driver can select it and then CONFIG_PWM would depend > on that. Would that even work? > One major reason for the new PWM framework is to be able to support arch independent PWM drivers, like those for companion chips with PWM capabilities. Restricting the config option to certain architectures wouldn't work. - Lars -- 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