From: Mike Anderson <andmike@us.ibm.com>
To: Patrick Mochel <mochel@osdl.org>
Cc: linux-scsi@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net,
mdharm-scsi@one-eyed-alien.net
Subject: Re: [RFC] scsi host sysfs support [0/4]
Date: Mon, 14 Apr 2003 17:25:02 -0700 [thread overview]
Message-ID: <20030415002502.GA7727@beaverton.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304141645210.15980-100000@cherise>
Patrick Mochel [mochel@osdl.org] wrote:
> > To fix the LLDDs would force drivers that have a parent bus not converted
> > to the driver model to take on a excessive amount of code to show up as a
> > class (properly).
>
> Then convert them to the driver model.
>
In past evaluations this looked like a large task, and was not a
requirement for getting the ref counting / release capabilities we
needed. Even though you did not like where the kobject was rooted the
parent / child and release functionality appears to be working.
> But, taking a step back, is SCSI a bus type? Yes, then it should go under
> bus/scsi/. You can implement an object under there, just as you would
> under scsi/
>
Ok I could root scsi_host under /bus/scsi.
-andmike
--
Michael Anderson
andmike@us.ibm.com
prev parent reply other threads:[~2003-04-15 0:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 18:37 [RFC] scsi host sysfs support [0/4] Mike Anderson
2003-04-14 18:39 ` [RFC] scsi host sysfs support [1/4] Mike Anderson
2003-04-14 18:40 ` [RFC] scsi host sysfs support [2/4] Mike Anderson
2003-04-14 18:41 ` [RFC] scsi host sysfs support [3/4] Mike Anderson
2003-04-14 18:42 ` [RFC] scsi host sysfs support [4/4] Mike Anderson
2003-04-14 23:02 ` [RFC] scsi host sysfs support [0/4] Patrick Mochel
2003-04-14 23:47 ` Mike Anderson
2003-04-14 23:48 ` Patrick Mochel
2003-04-15 0:25 ` Mike Anderson [this message]
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=20030415002502.GA7727@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=mdharm-scsi@one-eyed-alien.net \
--cc=mochel@osdl.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