From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Greg KH <gregkh@suse.de>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
linux-kernel@vger.kernel.org, Vojtech Pavlik <vojtech@suse.cz>,
Hannes Reinecke <hare@suse.de>,
Patrick Mochel <mochel@digitalimplant.org>,
airlied@linux.ie
Subject: Re: [RFC] subclasses in sysfs to solve world peace
Date: Fri, 16 Sep 2005 17:55:35 -0500 [thread overview]
Message-ID: <d120d5000509161555b021a3d@mail.gmail.com> (raw)
In-Reply-To: <20050916214841.GA13920@suse.de>
On 9/16/05, Greg KH <gregkh@suse.de> wrote:
> On Fri, Sep 16, 2005 at 02:21:53AM -0500, Dmitry Torokhov wrote:
> > > >
> > > > No, like your first picture, except 'interfaces/mice' will be a directory,
> > > > not a symlink, since it does not have class_device parent. I should have
> > > > said "Otherwise it gets added into _its_ class directory".
> > >
> >
> > Ok, this is _very_ raw and I am creating double symlinks somehow, but still
> > it shows it can be done:
> >
> > [dtor@core ~]$ tree /sys/class/input/
> > /sys/class/input/
> > |-- devices
> > | |-- input0
>
> Close, just drop the "devices" subdir, and you have my proposal, I'm
> glad we agree :)
>
No, not entirely agree. I _want_ devices subdir to separate objects of
different [sub]classes. We don;'t mix SCSI class_devices with USB, why
messing it here?
> > `-- interfaces
> > |-- event0 -> ../../../class/input/devices/input0/event0
>
> I don't see why we need the interfaces subdir at all.
>
For the same reasons you have hwmon stuff - one shoudl not hunt
through maze of subdirectories and filter unwanted data to get list of
objects of given class.
--
Dmitry
next prev parent reply other threads:[~2005-09-16 22:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 0:20 [RFC] subclasses in sysfs to solve world peace Greg KH
2005-09-16 0:58 ` Dmitry Torokhov
2005-09-16 1:46 ` Kay Sievers
2005-09-16 1:58 ` Dmitry Torokhov
2005-09-16 21:54 ` Greg KH
2005-09-16 1:04 ` Kay Sievers
2005-09-16 1:23 ` Dmitry Torokhov
2005-09-16 1:54 ` Kay Sievers
2005-09-16 2:03 ` Dmitry Torokhov
2005-09-16 2:14 ` Kay Sievers
2005-09-16 2:36 ` Dmitry Torokhov
2005-09-16 2:43 ` Kay Sievers
2005-09-16 3:10 ` Dmitry Torokhov
2005-09-16 7:21 ` Dmitry Torokhov
2005-09-16 21:48 ` Greg KH
2005-09-16 22:55 ` Dmitry Torokhov [this message]
2005-09-16 8:02 ` Vojtech Pavlik
2005-09-16 15:44 ` Dmitry Torokhov
2005-09-16 21:50 ` Greg KH
2005-09-16 22:56 ` Dmitry Torokhov
2005-09-17 0:48 ` Dave Airlie
2005-09-16 21:49 ` Greg KH
2005-09-16 7:59 ` Vojtech Pavlik
2005-09-16 21:55 ` Greg KH
2005-09-16 22:45 ` Dmitry Torokhov
2005-09-17 0:20 ` Antonino A. Daplas
-- strict thread matches above, loose matches on Subject: below --
2005-09-16 1:45 David Lang
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=d120d5000509161555b021a3d@mail.gmail.com \
--to=dmitry.torokhov@gmail.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 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.