From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753443Ab2HAI4v (ORCPT ); Wed, 1 Aug 2012 04:56:51 -0400 Received: from mail.skyhub.de ([78.46.96.112]:39795 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753220Ab2HAI4s (ORCPT ); Wed, 1 Aug 2012 04:56:48 -0400 Date: Wed, 1 Aug 2012 10:56:44 +0200 From: Borislav Petkov To: Thierry Reding Cc: Steven Rostedt , Dave Jones , Linux Kernel Subject: Re: awful kconfig help texts. Message-ID: <20120801085644.GA21303@liondog.tnic> Mail-Followup-To: Borislav Petkov , Thierry Reding , Steven Rostedt , Dave Jones , Linux Kernel References: <20120731151600.GA19412@redhat.com> <20120731170741.GA4735@x1.osrc.amd.com> <20120731172638.GE16873@home.goodmis.org> <20120731174249.GB4735@x1.osrc.amd.com> <20120801074742.GH29673@avionic-0098.adnet.avionic-design.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20120801074742.GH29673@avionic-0098.adnet.avionic-design.de> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? -- Regards/Gruss, Boris.