[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0702051322580.8424@woody.linux-foundation.org>
Date: Mon, 5 Feb 2007 13:28:55 -0800 (PST)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: David Woodhouse <dwmw2@...radead.org>
cc: Ingo Molnar <mingo@...e.hu>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [patch] MTD: fix DOC2000/2001/2001PLUS build error
On Mon, 5 Feb 2007, David Woodhouse wrote:
>
> No, you're thinking of something else. The use of 'select' just turns
> the problem backwards -- if _every_ SCSI hostadapter were to 'select
> SCSI' instead of depending on it, then I'd have to say 'n' to every damn
> one of them instead of being able to just say 'n' to SCSI as I can at
> the moment.
Right. Because for MOST scsi drivers, it's obvious that they are SCSI to
the user.
So we ask "do you want SCSI" in order to not ask a million questions that
a lot of people know a-priori that they don't want.
But if you cannot see that this is something TOTALLY DIFFERENT from USB
storage, you're either being obtuse on purpose, or just incapable of
understanding humans.
We should NEVER have had "USB_STORAGE" depending on SCSI. It'sa BUG. It's
a _stupid_ bug.
We should have done what is sane:
- make CONFIG_SCSI (as a "support the SCSI layer" be invisible to users,
because it's not a user decision.
- have a CONFIG_SCSI_DRIVER question for "do you want to be asked about
SCSI drivers" (and which also does "select SCSI" for you)
- make USB_STORAGE _also_ do the "select SCSI" thing.
In other words, you seem to be totally unable to grasp my argument. You
are arguing on TOTALLY IRRELEVANT TECHNICAL GROUNDS. That's not what the
Kconfig language is about. The Kconfig language and rules are about HUMAN
interaction.
So next time you say something about Kconfig, ask yourself: "What question
would a user want to see".
Any other question is pretty much totally irrelevant, and your "don't use
select" rule comes from your confusion that thinks that it's somehow about
machines and technical issues. It's not.
Linus
-
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