From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bottomley Subject: Re: [PATCH] Hidden scsi devices Date: 22 Jan 2004 14:46:13 -0500 Sender: linux-scsi-owner@vger.kernel.org Message-ID: <1074800777.1798.31.camel@mulgrave> References: <4010034A.3040903@us.ibm.com> <1074792163.2149.12.camel@mulgrave> <4010096D.4030205@us.ibm.com> <1074793813.2149.32.camel@mulgrave> <20040122194307.GH2611@beaverton.ibm.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from stat1.steeleye.com ([65.114.3.130]:1738 "EHLO hancock.sc.steeleye.com") by vger.kernel.org with ESMTP id S266413AbUAVTqj (ORCPT ); Thu, 22 Jan 2004 14:46:39 -0500 In-Reply-To: <20040122194307.GH2611@beaverton.ibm.com> List-Id: linux-scsi@vger.kernel.org To: Mike Anderson Cc: Brian King , Martin Peschke3 , SCSI Mailing List On Thu, 2004-01-22 at 14:43, Mike Anderson wrote: > Trying to understand the scope of support for the LLDD. While just > changing the device_type would be a small change, intercepting future > inquiry commands to ensure all future device_types returned this new > value would be larger. > > Is your comment to change the device type to stop binding also include > this intercept capability. No, this was just thinking about a short term fix in the driver (without having to propagate it through the mid layer). Lying to the mid layer always ends up being more trouble than it's worth. > It would seem that if in the future we would want some user space binding > control that adding this LLDD device_type modification would be more > code to clean out vs just not setting a no bind bit anymore. Yes, I think this is the correct future direction as well. James