From: Matt Domsch <Matt_Domsch@dell.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org,
Dmitry Torokhov <dtor_core@ameritech.net>,
Jon Smirl <jonsmirl@gmail.com>, Hannes Reinecke <hare@suse.de>
Subject: Re: [RFC][PATCH 2.6.13-rc1] driver core: subclasses
Date: Sat, 9 Jul 2005 08:04:14 -0500 [thread overview]
Message-ID: <20050709130414.GA6362@lists.us.dell.com> (raw)
In-Reply-To: <20050709024000.GA7608@kroah.com>
On Fri, Jul 08, 2005 at 07:40:00PM -0700, Greg KH wrote:
> On Fri, Jul 08, 2005 at 05:54:48PM -0500, Matt Domsch wrote:
> > The below patch is a first pass at implementing subclasses, for review
> > and comment.
>
> Oops, when you mentioned this on irc, I thought you were referring to
> class_devices not classes. I don't want classes to be able to be
> nested, only class devices.
>
> I don't see a need for nested classes, as I thought the input thread had
> resolved itself so that it didn't need it (but I stopped paying
> attention, sorry, so I might be wrong here...)
The tailing part of the thread is here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=111873628324649&w=2
http://marc.theaimsgroup.com/?l=linux-hotplug-devel&m=111877313202313&w=2
where Hannes and Dmitry seemed to indicate (to my reading) that they
were looking for subclasses. Perhaps it's not necessary.
> Why can't you just use class_device's that can have children? That way
> the /sys/block stuff could be converted to also use this.
I will investigate.
Thanks,
Matt
--
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2005-07-09 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 22:54 [RFC][PATCH 2.6.13-rc1] driver core: subclasses Matt Domsch
2005-07-09 2:40 ` Greg KH
2005-07-09 13:04 ` Matt Domsch [this message]
2005-07-10 6:35 ` Dmitry Torokhov
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=20050709130414.GA6362@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=dtor_core@ameritech.net \
--cc=greg@kroah.com \
--cc=hare@suse.de \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@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