public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Belay <ambx1@neo.rr.com>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>,
	Vojtech Pavlik <vojtech@suse.cz>, Hannes Reinecke <hare@suse.de>,
	Patrick Mochel <mochel@digitalimplant.org>,
	airlied@linux.ie
Subject: Re: [PATCH] nesting class_device in sysfs to solve world peace
Date: Tue, 11 Oct 2005 00:00:28 -0400	[thread overview]
Message-ID: <20051011040028.GA21135@neo.rr.com> (raw)
In-Reply-To: <200509300032.50408.dtor_core@ameritech.net>

On Fri, Sep 30, 2005 at 12:32:49AM -0500, Dmitry Torokhov wrote:
> 
> I firmly believe that creating sub-classes (which solves hotplug issues)
> and linking sub-class devices to their parent via 'device' link, much like
> we link top-level class device to their physical parent devices (which
> solves 2, 3 and 4) is much cleanier way. It provides everything that your
> implementation does plus allows different views useful for other tasks
> besides udev.

Hi Dmitry,

Could you please outline the class device requirements for the input
subsystem?  Specifically I'm interested in the class -> subclass layering.
I'm trying to understand what is needed and how the input subsystem should
be structured.

I can think of other subystems that might benefit from class layering.  One
example might be wireless cards: net and net/wireless.  In this case devices
that belong to class "wireless" would inherit all of the capabilities of the
"net" class and also implement the "wireless"-specific feature set.

Thanks,
Adam

      parent reply	other threads:[~2005-10-11  3:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 23:31 [PATCH] nesting class_device in sysfs to solve world peace Greg KH
2005-09-30  5:32 ` Dmitry Torokhov
2005-10-06  0:09   ` Greg KH
2005-10-06  0:26     ` Greg KH
2005-10-06  0:29     ` Greg KH
2005-10-06  6:29     ` Dmitry Torokhov
2005-10-06 12:00       ` Michael Tokarev
2005-10-06 17:40         ` Dmitry Torokhov
2005-10-06 21:22       ` Greg KH
2005-10-06 21:59         ` Dmitry Torokhov
2005-10-11  4:00   ` Adam Belay [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=20051011040028.GA21135@neo.rr.com \
    --to=ambx1@neo.rr.com \
    --cc=airlied@linux.ie \
    --cc=dtor_core@ameritech.net \
    --cc=gregkh@suse.de \
    --cc=hare@suse.de \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@digitalimplant.org \
    --cc=vojtech@suse.cz \
    /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