public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Thierry Reding <thierry.reding@avionic-design.de>
Subject: Re: awful kconfig help texts.
Date: Tue, 31 Jul 2012 19:07:41 +0200	[thread overview]
Message-ID: <20120731170741.GA4735@x1.osrc.amd.com> (raw)
In-Reply-To: <20120731151600.GA19412@redhat.com>

On Tue, Jul 31, 2012 at 11:16:00AM -0400, Dave Jones wrote:
> 
> PWM Support (PWM) [N/y/?] (NEW) ?
> 
> CONFIG_PWM:
> 
> This enables PWM support through the generic PWM framework.
> 
> 
> Well that's.. enlightening.

Oh, there's one more enlightening sentence in the help:

"You only need to enable this, if you also want to enable one or more of
the PWM drivers below."

Got it? :-)

> I'm picking on PWM here, but this isn't an
> isolated case.  Every merge window we see a slew of new options with useless
> help texts. They may as well be non-existent. (Actually in some cases, they are).
> 
> If someone has to read the code to find out what the driver is, your help text probably sucks.
> 
> 
> (I'll leave "why does this option even show up on x86" as a separate rant)

Thierry, can you guys please fix this?

Thanks.

-- 
Regards/Gruss,
Boris.

  reply	other threads:[~2012-07-31 17:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 15:16 awful kconfig help texts Dave Jones
2012-07-31 17:07 ` Borislav Petkov [this message]
2012-07-31 17:26   ` Steven Rostedt
2012-07-31 17:42     ` Borislav Petkov
2012-08-01  7:47       ` Thierry Reding
2012-08-01  8:56         ` Borislav Petkov
2012-08-01  9:21           ` Lars-Peter Clausen
2012-08-01  9:26             ` Borislav Petkov
2012-08-01  9:38               ` Lars-Peter Clausen
2012-08-01 10:04                 ` Borislav Petkov
2012-08-01 10:56                   ` Lars-Peter Clausen
2012-08-01 12:46                     ` Steven Rostedt
2012-08-01 13:18                       ` Lars-Peter Clausen
2012-08-07 18:25               ` Mark Brown
2012-07-31 18:43   ` Dave Jones
2012-07-31 22:11     ` Borislav Petkov
2012-08-01  7:43   ` Thierry Reding
2012-08-01  9:28     ` Jan Engelhardt
2012-08-16  9:54   ` Thierry Reding
2012-08-16 11:10     ` Borislav Petkov
2012-08-16 12:05       ` Thierry Reding
2012-08-17  6:11         ` Thierry Reding
2012-08-17  7:00           ` Borislav Petkov
2012-08-17  7:19             ` Thierry Reding
2012-08-20  2:34           ` Cam Hutchison

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120731170741.GA4735@x1.osrc.amd.com \
    --to=bp@alien8.de \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thierry.reding@avionic-design.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox