From: James Bottomley <James.Bottomley@steeleye.com>
To: Mike Anderson <andmike@us.ibm.com>
Cc: Brian King <brking@us.ibm.com>,
Martin Peschke3 <MPESCHKE@de.ibm.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Hidden scsi devices
Date: 22 Jan 2004 14:46:13 -0500 [thread overview]
Message-ID: <1074800777.1798.31.camel@mulgrave> (raw)
In-Reply-To: <20040122194307.GH2611@beaverton.ibm.com>
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
next prev parent reply other threads:[~2004-01-22 19:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 15:57 [PATCH] Hidden scsi devices Martin Peschke3
2004-01-22 17:07 ` Brian King
2004-01-22 17:22 ` James Bottomley
2004-01-22 17:33 ` Brian King
2004-01-22 17:50 ` James Bottomley
2004-01-22 18:42 ` Mike Anderson
2004-01-22 19:43 ` Mike Anderson
2004-01-22 19:46 ` James Bottomley [this message]
2004-01-22 20:13 ` Brian King
-- strict thread matches above, loose matches on Subject: below --
2004-01-22 15:21 Brian King
2004-01-22 15:50 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1074800777.1798.31.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=MPESCHKE@de.ibm.com \
--cc=andmike@us.ibm.com \
--cc=brking@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox