From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Wilcox Subject: Re: Possible bug in SCSI Kconfig Date: Thu, 23 Oct 2008 11:39:18 -0600 Message-ID: <20081023173917.GP26094@parisc-linux.org> References: <1224702340.6851.20.camel@localhost.localdomain> <1224704659.6851.28.camel@localhost.localdomain> <4900B4B9.4050103@s5r6.in-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from palinux.external.hp.com ([192.25.206.14]:51989 "EHLO mail.parisc-linux.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753101AbYJWRjV (ORCPT ); Thu, 23 Oct 2008 13:39:21 -0400 Content-Disposition: inline In-Reply-To: <4900B4B9.4050103@s5r6.in-berlin.de> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Stefan Richter Cc: James Bottomley , Fabio Comolli , Linux Kernel Mailing List , sam@ravnborg.org, linux-scsi On Thu, Oct 23, 2008 at 07:30:33PM +0200, Stefan Richter wrote: > - scsi_wait_scan is a special method to wait for devices during boot > which only works with some hardware types. More general methods are > available and have been in use far longer than scsi_wait_scan > exists. Nobody fundamentally needs scsi_wait_scan, it is only a > convenient tool for some users who choose to use it. > Special features are traditionally per default off in Kconfig and > are supposed to be actively enabled. What 'general methods' would those be? -- 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."