From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Kconfig text confusion: Battery Class Support?
Date: Sun, 06 May 2007 22:06:52 +1000 [thread overview]
Message-ID: <1178453212.7731.10.camel@localhost.localdomain> (raw)
Hi all,
I know writing decent Kconfig help entries is an obscure art, but can
we please try harder to make the help, y'know, helpful? See below for
my experience with 2.6.21-mm1.
How come the Kconfig help for EXTERNAL_POWER says "is mandatory for
battery class support" and I still get prompted for "Battery class
support" when I say N?
How come both these entries are of form "Foo (FOO)? -- Say Y here to
enable foo."? Shouldn't we assume the reader knows what Y means?
How about:
Battery class support (BATTERY) [N/m/y/?] (NEW) ?
This allows battery monitoring by userspace via sysfs (if
available) and/or APM kernel interface (if selected below). Say
Y or M if building a kernel for a laptop.
I don't even understand the CONFIG_EXTERNAL_POWER enough to comment on
that one 8(
Rusty.
==
*
* External power support
*
External power kernel interface (EXTERNAL_POWER) [N/m/y/?] (NEW) ?
Say Y here to enable kernel external power detection interface,
like AC or USB. Information also will exported to userspace via
/sys/class/external_power/ directory.
This interface is mandatory for battery class support.
External power kernel interface (EXTERNAL_POWER) [N/m/y/?] (NEW)
*
* Battery devices
*
Battery class support (BATTERY) [N/m/y/?] (NEW) ?
Say Y here to enable battery class support. This allows battery
monitoring by userspace via sysfs (if available) and/or APM
kernel interface (if selected below).
Battery class support (BATTERY) [N/m/y/?]
next reply other threads:[~2007-05-06 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 12:06 Rusty Russell [this message]
2007-05-06 20:27 ` Kconfig text confusion: Battery Class Support? Anton Vorontsov
2007-05-06 23:06 ` Rusty Russell
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=1178453212.7731.10.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/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