From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Wilcox Subject: Re: Asynchronous scsi scanning Date: Tue, 15 May 2007 11:29:06 -0600 Message-ID: <20070515172905.GJ10562@parisc-linux.org> References: <1179073116.3723.45.camel@mulgrave.il.steeleye.com> <1179153096.3703.23.camel@mulgrave.il.steeleye.com> <17841.simon.1179228389@5ec7c279.invalid> <20070515120228.GI10562@parisc-linux.org> <4649E03A.1090004@simon.arlott.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4649E03A.1090004@simon.arlott.org.uk> Sender: linux-kernel-owner@vger.kernel.org To: Simon Arlott Cc: James Bottomley , Dave Jones , Linux Kernel Mailing List , linux-scsi@vger.kernel.org, kernel-packagers@vger.kernel.org List-Id: linux-scsi@vger.kernel.org On Tue, May 15, 2007 at 05:30:50PM +0100, Simon Arlott wrote: > On 15/05/07 13:02, Matthew Wilcox wrote: > >It's easy to suggest a sysfs attribute. What you've failed to do is > >suggest the pathname of the sysfs attribute, the contents of it, or the > >semantics of it (read-only? read-write? write-only? blocking?) > > I would assume that should be up to SCSI users/maintainer(s). The only > thing I use the SCSI driver for is usb-storage/ATAPI. Then you're not so much "suggesting a sysfs attribute" as whining. > >I'd *really* like to hear from distro people. What is the most > >convenient way for you to implement "load all the scsi modules, then > >wait until all devices are found"? James and I had thought that loading > >a new module would be the easiest way for you, but it seems inconvenient > >for you. > > It's inconvenient for people who *don't* use it to be unable to stop the > module being built and installed. Why? You're not forced to load the module. In what way does it inconvenience you? Nobody's making you run 'make modules_install'. I often forget to myself.