From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Anderson Subject: Re: Notify about errors during initialization Date: Tue, 6 Jan 2004 10:08:14 -0800 Sender: linux-scsi-owner@vger.kernel.org Message-ID: <20040106180814.GA2119@beaverton.ibm.com> References: <20040105021047.GD30408@one-eyed-alien.net> <20040105221302.A7678@infradead.org> <20040105233221.GC1936@beaverton.ibm.com> <20040106161731.A17858@infradead.org> <20040106091538.A10957@beaverton.ibm.com> <20040106171843.A18507@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from e33.co.us.ibm.com ([32.97.110.131]:22936 "EHLO e33.co.us.ibm.com") by vger.kernel.org with ESMTP id S264918AbUAFSEb (ORCPT ); Tue, 6 Jan 2004 13:04:31 -0500 Content-Disposition: inline In-Reply-To: <20040106171843.A18507@infradead.org> List-Id: linux-scsi@vger.kernel.org To: Christoph Hellwig Cc: Patrick Mansfield , Alan Stern , James Bottomley , Matthew Dharm , USB Storage List , SCSI development list Christoph Hellwig [hch@infradead.org] wrote: > On Tue, Jan 06, 2004 at 09:15:39AM -0800, Patrick Mansfield wrote: > > Why not trigger off the scsi_host hotplug event? Though we will have races > > similiar to udev where the sysfs attribute files are created after the > > hotplug event - we really ought to have a device_init/setup, create the > > sysfs files, then device_add/enable. > > Because some drivers (like the ieee1394) don't want scanning to happen. > They can easily chose that by not sending a scan event. > Couldn't the user space also set the policy to scan or not scan? It would seem that user space would be more flexible and not need a new api (Just do not call scsi_scan_host). -andmike -- Michael Anderson andmike@us.ibm.com