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:48:10 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-105036428813962@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105034546325461@msgid-missing>
On Mon, 14 Apr 2003, Mike Anderson wrote:
> Patrick Mochel [mochel@osdl.org] wrote:
> > 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.
> >
>
> 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.
> > 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.
> >
>
> Where are the attributes written down for evaluating important vs not
> important subsystems.
They're not - they're completely subjective, and I reserve the right to
reserve that right. Basically, only subsystems that are always present
should be in the top-level directory.
Sure, networking may not always be present, but that case is rare, and as
I said before, it's on its way to becoming a device class.
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/
> > 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.
>
> What interfaces am I abusing. I have used api's documented by you.
Hopefully none ATM, though that doesn't count the code I've seen in the
past.
-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:48 UTC|newest]
Thread overview: 10+ 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
2003-04-14 23:47 ` Mike Anderson
2003-04-14 23:48 ` Patrick Mochel [this message]
2003-04-15 0:25 ` Mike Anderson
-- strict thread matches above, loose matches on Subject: below --
2003-04-14 18:37 Mike Anderson
2003-04-14 23:02 ` Patrick Mochel
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-105036428813962@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 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.