From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Adrian Bunk <bunk@kernel.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Sam Ravnborg <sam@ravnborg.org>, Al Boldi <a1426z@gawab.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
David Brownell <david-b@pacbell.net>, Greg KH <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/5] USB Kconfig: Select SCSI for USB Mass Storage support
Date: Sun, 06 Jan 2008 14:57:38 +0100 [thread overview]
Message-ID: <4780DE52.1090402@s5r6.in-berlin.de> (raw)
In-Reply-To: <20080106133854.GH2082@does.not.exist>
Adrian Bunk wrote:
> On Sun, Jan 06, 2008 at 02:13:09PM +0100, Stefan Richter wrote:
>> Module autoloading is quite different.
>
> Both are "hardware -> required kernel support" mappings.
>
> I know that people don't like this idea since the CML2 discussions, but
> there even don't seem to be any big problems if anyone wants to put all
> the pieces together and assemble a suitable .config only based on the
> autodetection tools of some distribution and without asking the user
> any questions.
How to autodetect that the user is going to buy gadget xyz next week?
(OK, he can re-run autodetection then, although that's not a
particularly economic strategy.)
How to autodetect POSIX_MQUEUE, HZ_250, HOTPLUG_PCI, ...?
[...]
>> This /is/ what we are currently doing, not "worse than what we are
>> currently doing". We
>> - sensibly modularize our software,
>> - tell the user which software components there are,
>> - what they are for,
>> - how they depend on each other,
>> - make it easy enough for the user to navigate in the dependency
>> graph,
>> - provide fundamental safeguards and checks for a proper software
>> configuration. (Well, we actually walk on thin ice whenever we
>> use the 'select' keyword.)
>> ...
>
> You miss the fundamental point:
>
> The vast majority of kconfig users are _not_ kernel hackers, and they
> neither know nor want to know anything about kernel internals - they
> just want to build a kernel suitable for their system.
I don't miss the point. I just say what we realistically can do. And I
might add, we should try hard to achieve good results in each of the
points I listed.
> You want to make an UI easier to use for the developers but harder to
> use for the users, and that's a bad deal.
No, I don't.
(I have "worked" long enough in enduser support, and still am doing
support, to not have completely lost an eye for enduser needs. Or so I
believe.)
--
Stefan Richter
-=====-==--- ---= --==-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-01-06 13:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 15:41 Al Boldi
2008-01-05 18:42 ` David Brownell
2008-01-05 19:30 ` Randy Dunlap
2008-01-05 21:03 ` Adrian Bunk
2008-01-05 21:09 ` Sam Ravnborg
2008-01-05 23:22 ` Randy Dunlap
2008-01-05 23:45 ` Adrian Bunk
2008-01-06 0:35 ` Stefan Richter
2008-01-06 0:58 ` Adrian Bunk
2008-01-06 11:29 ` Stefan Richter
2008-01-06 11:59 ` Adrian Bunk
2008-01-06 12:32 ` Stefan Richter
2008-01-06 12:58 ` Adrian Bunk
2008-01-06 13:23 ` Stefan Richter
2008-01-06 12:18 ` Stefan Richter
2008-01-06 12:37 ` Adrian Bunk
2008-01-06 13:13 ` Stefan Richter
2008-01-06 13:38 ` Adrian Bunk
2008-01-06 13:55 ` Sam Ravnborg
2008-01-06 13:57 ` Stefan Richter [this message]
2008-01-06 14:45 ` david
2008-01-06 13:41 ` Stefan Richter
2008-01-06 15:05 ` david
2008-01-06 14:08 ` Stefan Richter
2008-01-06 17:11 ` Alan Stern
2008-01-06 18:07 ` Stefan Richter
2008-01-06 1:01 ` Randy Dunlap
2008-01-06 11:54 ` Stefan Richter
2008-01-06 12:05 ` Adrian Bunk
2008-01-06 12:41 ` Stefan Richter
2008-01-06 5:03 ` Al Boldi
2008-01-06 14:39 ` Stefan Richter
2008-01-06 17:07 ` Al Boldi
2008-01-06 17:50 ` Stefan Richter
2008-01-06 18:01 ` Stefan Richter
2008-01-06 18:23 ` Sam Ravnborg
2008-01-05 20:40 ` Stefan Richter
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=4780DE52.1090402@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=a1426z@gawab.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--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®