[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46EAAAC1.3050409@s5r6.in-berlin.de>
Date: Fri, 14 Sep 2007 17:37:37 +0200
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Adrian Bunk <bunk@...nel.org>
CC: Jeff Garzik <jeff@...zik.org>, Andi Kleen <andi@...stfloor.org>,
James Bottomley <James.Bottomley@...elEye.com>,
Folkert van Heusden <folkert@...heusden.com>,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: sata & scsi suggestion for make menuconfig
Adrian Bunk wrote:
> On Fri, Sep 14, 2007 at 04:54:07PM +0200, Stefan Richter wrote:
>> The patch which is discussed here is specifically targeted towards users
>> who are convinced that they can migrate to different drivers without
>> reading Kconfig help texts.
>
> Nothing about the patch is only about migration.
>
> The same applies if you configure a kernel from scratch.
>
> Do "make menuconfig" with the .config you are normally using, count the
> number of options that are visible, and ask yourself whether we can
> really expect users to read the help texts for every single option shown.
>
> People mostly read help texts for options where they don't understand
> what this option is about - and "Serial ATA" therefore is an option that
> is likely to get enabled without the user looking at the help text.
If you create .config from scratch, then you can get away without
reading help texts if you have a target with minimal hardware and
protocols requirements and you know all the subsystems involved.
In all other cases, you theoretically need to read all help texts (minus
the ones that don't appear because you deselect entire subsystems). In
practice, this takes too much time, hence you take an existing .config
(yours or somebody else's) and go from there.
Whenever one enables an option for the first time, it would IMO be
foolish to ignore its help text.
--
Stefan Richter
-=====-=-=== =--= -===-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists