From: "Joseph M. Hinkle" <dunsalen@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: menuconfig information deficiencies
Date: Sat, 21 Aug 2004 06:52:50 -0700 (PDT) [thread overview]
Message-ID: <20040821135250.41480.qmail@web41704.mail.yahoo.com> (raw)
There are a few places in menuconfig where no
information is given and should be. If something is
compiled as a module, the module name should at least
be listed. A short reason for including the item
should be given, and a long one is better. Simply
"You need this" or "If in doubt say Y" is
insufficient.
In kernel 2.6.8: (If information isn't present here,
it probably never has been in any kernel)
ATA/ATAPI/MFM/RLL Support
IDE Taskfile IO
"It is safe to say Y to this question in most
cases"
Oh? And what might the cases be where it is not? What
are typical indications this might cause trouble?
ATA/ATAPI/MFM/RLL Support
generic/default IDE chipset support
"If unsure say Y"
Is this essential if one knows the IDE chipset as
obtained from lspci? What is the module name if
compiled as a module?
ATA/ATAPI/MFM/RLL Support
Generic PCI IDE Chipset Support
"There is no help for this option"
Why is that? Must it never be used? Why is it
selected by default? Does it need to be selected if
the IDE chipset is known?
ATA/ATAPI/MFM/RLL Support
PROMISE PDC202{68|69|70|71|75|76|77} support
"There is no help available for this kernel
option"
None of the other specific chipset items fail to
mention the module name either. At least the others
make some attempt to keep the configurer informed of
basic issues.
SCSI device support
SCSI Transport Attributes
Parallel SCSI (SPI) Transport Attributes
No mention of the module name is made.
FiberChannel Transport Attributes
No mention of the module name is made.
SCSI low-level drivers
3ware 5/6/78xxx ATA-RAID support
3ware 9xxx SATA-RAID support
No mention of the module name is made.
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
reply other threads:[~2004-08-21 13:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040821135250.41480.qmail@web41704.mail.yahoo.com \
--to=dunsalen@yahoo.com \
--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
all inboxes | Powered by JetHome®