From: Douglas Gilbert <dougg@torque.net>
To: Bodo Eggert <7eggert@gmx.de>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: Bad escriptions in Kconfig
Date: Mon, 31 Dec 2007 10:16:43 -0500 [thread overview]
Message-ID: <477907DB.8030406@torque.net> (raw)
In-Reply-To: <alpine.LSU.0.999.0712311313050.3761@be1.lrz>
Bodo Eggert wrote:
> In some of the Kconfig files, the options are not adequately decribed. I
> collected a few of the bad descriptions I found:
>
>
> ---
> Lowlevel video output switch controls (VIDEO_OUTPUT_CONTROL) [M/n/y/?] (NEW) ?
>
> This framework adds support for low-level control of the video
> output switch.
> ---
>
> - What is THE video output switch and why would I need low level control?
>
> - Frameworks should be auto-selected like libraries, shouldn't they?
>
> - WTF is this a module?
>
>
> -------------
> ---
> Auxiliary Display support (AUXDISPLAY) [N/y/?] (NEW) ?
>
> Say Y here to get to see options for auxiliary display drivers.
> This option alone does not add any kernel code.
> ---
>
> - If I knw what an axilary display was, I would not read this help text!
>
> - After digging some time, I discovered that all Auxdisplays are parallel
> port devices.
> Rename to "Parallel port display device support"?
>
>
> -------------
> ---
> Transformation user configuration interface (XFRM_USER) [N/m/y/?] (NEW)
>
> Support for Transformation(XFRM) user configuration interface
> like IPsec used by native Linux tools.
>
> If unsure, say Y.
> ---
>
> - I'm not sure if these words combine to a sentence.
> - I can't tell if IPSEC is the only user or if I'd break other parts by not
> saying 'Y'. OTOH, I don't want to bloat my kernel ...
> - What's a native linux tool?
>
>
> -------------
> ---
> SCSI target support (SCSI_TGT) [N/m/y/?] (NEW) ?
>
> If you want to use SCSI target mode drivers enable this option.
> If you choose M, the module will be called scsi_tgt.
> ---
>
> What TF is a SCSI target mode, what is a target mode driver?
Heard of google :-)
For explanations of SCSI (and other storage) terminology
reference could be made to SAM-3 or SAM-4 drafts (because
the real standards cost money) at www.t10.org .
Perhaps many other subsections in the kernel could have
similar references.
Doug Gilbert
next prev parent reply other threads:[~2007-12-31 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 12:26 Bad escriptions in Kconfig Bodo Eggert
2007-12-31 15:16 ` Douglas Gilbert [this message]
2007-12-31 15:47 ` Matthew Wilcox
2007-12-31 16:34 ` Douglas Gilbert
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=477907DB.8030406@torque.net \
--to=dougg@torque.net \
--cc=7eggert@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).