Re: [RFC][PATCH 2.6.13-rc1] driver core: subclasses

[Greg KH <greg@kroah.com>]

On Fri, Jul 08, 2005 at 05:54:48PM -0500, Matt Domsch wrote:
> Greg,
> 
> The below patch is a first pass at implementing subclasses, for review
> and comment.
> 
> As a test, I modified drivers/input/input.c to allocate a new class,
> and register it as a subclass.
> 
> Before:
> 
> /sys/class/input/
> /sys/class/input_device/
> 
> After:
> /sys/class/input/input_device/

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...)

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.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/