From: Christoph Hellwig <hch@infradead.org>
To: Brian King <brking@us.ibm.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [RFC] IBM Power RAID driver (ipr)
Date: Thu, 22 Jan 2004 14:02:48 +0000 [thread overview]
Message-ID: <20040122140248.C11283@infradead.org> (raw)
In-Reply-To: <400EE5E6.9080709@us.ibm.com>; from brking@us.ibm.com on Wed, Jan 21, 2004 at 02:49:42PM -0600
On Wed, Jan 21, 2004 at 02:49:42PM -0600, Brian King wrote:
> How about a flag in the scsi_device struct that an LLD could set in
> slave_configure, which would prevent upper layer drivers from binding
> to it?
I'm not that happy about this. But the other solutions I could think
of are ven worse.
> Then these devices could be found through the normal scsi scan
> and would have nice sysfs entries and sg devices for them. Not sure what
> we would call the flag... psuedo_device, fake_device?
ghost? hidden?
Could you cook up a patch?
next prev parent reply other threads:[~2004-01-22 14:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 21:59 [RFC] IBM Power RAID driver (ipr) Brian King
2004-01-16 23:01 ` Muli Ben-Yehuda
2004-01-16 23:46 ` Brian King
2004-01-18 14:10 ` Anton Blanchard
2004-01-19 16:16 ` Brian King
2004-01-19 18:34 ` Christoph Hellwig
2004-01-19 19:33 ` Mike Anderson
2004-01-19 19:35 ` Christoph Hellwig
2004-01-20 5:57 ` Douglas Gilbert
2004-01-20 13:21 ` Christoph Hellwig
2004-01-19 20:30 ` Brian King
2004-01-20 13:38 ` Christoph Hellwig
2004-01-20 16:41 ` Brian King
2004-01-20 17:18 ` Mike Anderson
2004-01-20 18:01 ` Christoph Hellwig
2004-01-20 19:13 ` Brian King
2004-01-20 19:28 ` Christoph Hellwig
2004-01-20 20:13 ` Brian King
2004-01-21 20:49 ` Brian King
2004-01-22 14:02 ` Christoph Hellwig [this message]
2004-01-22 16:39 ` Patrick Mansfield
2004-01-22 16:56 ` Patrick Mansfield
2004-01-22 17:09 ` Brian King
2004-01-22 17:27 ` Patrick Mansfield
2004-01-22 17:33 ` Brian King
2004-01-20 20:35 ` Patrick Mansfield
2004-01-20 22:37 ` Brian King
2004-01-20 22:39 ` 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=20040122140248.C11283@infradead.org \
--to=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.