Messages in this thread | | | Date | Mon, 22 Jun 2009 05:02:30 -0600 | From | Matthew Wilcox <> | Subject | Re: [PATCH update 2] SCSI: explain the hidden scsi_wait_scan Kconfig variable |
| |
On Mon, Jun 22, 2009 at 09:57:01AM +0100, Alan Cox wrote: > On Thu, 18 Jun 2009 21:03:23 +0200 (CEST) > Stefan Richter <stefanr@s5r6.in-berlin.de> wrote: > > > People keep sending patches to expose CONFIG_SCSI_WAIT_SCAN as a tunable > > item. These patches aren't accepted upstream, so let's stop the ongoing > > irritation of people due to the unconditionally installed module and its > > Kconfig symbol. > > How about the other possibility. People keepmaking it tunable because it > makes sense for it to be tunable. Far better IMHO to make it tunable "if > EMBEDDED"
It doesn't make sense for it to be tunable.
All it does is control whether or not scsi_wait_scan.ko is built. Everyone who's complained about it has been of the form "I turned off all modules, but this module gets built anyway". For them, the answer is simple: Don't run "make modules_install".
-- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step."
| |