From: Patrick Mochel <mochel@osdl.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [RFC] scsi host sysfs support [0/4]
Date: Mon, 14 Apr 2003 23:02:58 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-105036153912053@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105034546325461@msgid-missing>
On Mon, 14 Apr 2003, Mike Anderson wrote:
> This patch set is against 2.5.67 current. It will not apply to scsi-miscs-2.5
> as the decl_subsys macro has added a third argument.
>
> This patch set changes the sysfs support for scsi hosts.
> - Removes the previous support of shost_devclass device class.
>
> - Modifies scsi_debug to support the new order of object cleanup and also
> changes the structure of sdebug_host_info to help in object cleanup.
>
> - Creates a scsi subsystem. This is rooted at the top of the sysfs tree.
No. Period.
This will not fly. Not now, and not ever.
> - Creates a scsi_host subsystem under the scsi subsystem. Modified the
> cleanup in scsi remove host. Switched to a kobject embedded in
> scsi_host. If a driver has not be converted to the driver model or does
> not use the scsi_set_device call it will still show up in the scsi_host
> subsystem, but will not have a symlink to the parent.
>
> The usage of driver model classes for scsi hosts was removed because many
> of our drivers have not been converted to the driver model so this gave an
> inconsistent model to count on for cleanup and migration of some the
> procfs support. I tried adding some fake structures to use classes, but it
> failed to cleanup properly do to asymmetric cleanup interfaces in the core
> code and also did not seem like the correct direction to go.
Then you need to fix the code, or do some work to fix up the class
support. You have no right to promote scsi to a top-level subsystem, and I
will not support. I'll not even read the rest of the patches.
I realize that block and net are top-level subsystems. They are there for
two reasons - 1) they _are_ that important, and 2) they're temporary steps
to them being converted to classes.
I realize that you think SCSI is just as important as block devices or net
devices, but it's just not true for most systems, and I will not open the
flood gates for you to abuse even more interfaces.
Thanks,
-pat
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2003-04-14 23:02 UTC|newest]
Thread overview: 5+ 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 23:02 ` Patrick Mochel [this message]
2003-04-14 23:47 ` Mike Anderson
2003-04-14 23:48 ` Patrick Mochel
2003-04-15 0:25 ` Mike Anderson
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=marc-linux-hotplug-105036153912053@msgid-missing \
--to=mochel@osdl.org \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).