From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luben Tuikov Subject: Re: [linux-usb-devel] Re: [PATCH] USB changes for 2.5.58 Date: Fri, 24 Jan 2003 16:09:37 -0500 Sender: linux-scsi-owner@vger.kernel.org Message-ID: <3E31AB91.9080400@splentec.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Id: linux-scsi@vger.kernel.org To: Alan Stern Cc: Matthew Dharm , Oliver Neukum , Doug Ledford , David Brownell , Mike Anderson , Greg KH , linux-usb-devel@lists.sourceforge.net, Linux SCSI list Alan Stern wrote: > Are you aware that you are contradicting yourself? > > On Fri, 24 Jan 2003, Luben Tuikov wrote: > > >>A LLDD should and must *not* call scsi_unregister_host(). This brakes >>all hierarchy. > What I probably meant is the detect()/release() pair; release() itself normally calls scsi_unregister(host); the point is that it got nudged from ``above'', i.e. SCSI Core. How can a LLDD be certain that it can safely call scsi_unregister_host() whenever it wishes? As Doug pointed out this leads to problems. Furhtermore, are we talking about scsi_unregister_host() or scsi_unregister(host)? The former does drivers and the latter does hosts. This would mean that my original statement was nevertheless correct, how can a LLDD decide to unload itself safely? -- Luben