From: Arjan van de Ven <arjan@infradead.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Sam Ravnborg <sam@ravnborg.org>, Dave Jones <davej@redhat.com>,
linux-ide@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: tighten ATA kconfig dependancies
Date: Sat, 15 Jul 2006 12:56:43 +0200 [thread overview]
Message-ID: <1152961003.3114.15.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060715102825.GR3633@stusta.de>
> > the point is that it doesn't fall out naturally, and thus things get
> > needlessly missed.
>
> It seems the main question is:
> Is the kernel configuration mainly designed for users or for developers?
>
> For users, showing drivers for hardware that is not present on their
> platform only causes confusion.
well Aunt Tilly gets confused by all hardware that is not present on her
machine; she has no idea what a platform is. By that reasoning, we
should make kconfig hide all non-present hardware.
Also I think there is no difference in confusion between showing 10 or
15 IDE chipsets. Either the user knows what he has (and then it doesn't
matter) or those 10 are too much already.
next prev parent reply other threads:[~2006-07-15 10:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-15 5:34 Dave Jones
2006-07-15 5:49 ` Arjan van de Ven
2006-07-15 6:38 ` Sam Ravnborg
2006-07-15 6:45 ` Arjan van de Ven
2006-07-15 10:28 ` Adrian Bunk
2006-07-15 10:56 ` Arjan van de Ven [this message]
2006-07-16 9:13 ` Adrian Bunk
2006-07-24 3:05 ` Alan Cox
[not found] <6yL2J-7rR-1@gated-at.bofh.it>
[not found] ` <6yLco-7DB-1@gated-at.bofh.it>
2006-07-15 18:38 ` Bodo Eggert
2006-07-16 5:58 ` Sam Ravnborg
2006-07-16 6:04 ` Arjan van de Ven
2006-07-16 6:17 ` Sam Ravnborg
2006-07-16 18:14 Randy Dunlap
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=1152961003.3114.15.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=davej@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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®