From: Kyle Moffett <mrmacman_g4@mac.com>
To: Greg KH <greg@kroah.com>
Cc: Patrick Mochel <mochel@digitalimplant.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Updates to sysfs_create_subdir()
Date: Mon, 28 Nov 2005 20:10:36 -0500 [thread overview]
Message-ID: <37362F2B-D74A-4A40-905B-B25264B6C4AB@mac.com> (raw)
In-Reply-To: <20051128204950.GC17740@kroah.com>
On Nov 28, 2005, at 15:49, Greg KH wrote:
> On Wed, Nov 23, 2005 at 01:56:29PM -0800, Patrick Mochel wrote:
>> The patch below addresses this issue by parsing the subdirectory
>> name and creating any parent directories delineated by a '/'.
>
> Generally I never liked parsing stuff like this in the kernel (proc
> and devfs both do this). That being said, I do see the need to
> make subdirs like this easier.
>
> But what about cleanups? If I create an attribute group "foo/baz/
> x/" and then remove it, will the subdirectories get cleaned up
> too? What about if I had created a group "foo/baz/y/" after the
> "x" one? Or just "foo/baz"?
If the kernel gets this, then udev needs to allow attributes with
more generic paths too. It would be nice if I could use this [Pulled
from the sample udev output halfway down this page: http://
www.reactivated.net/writing_udev_rules.html#identify-sysfs].
BUS="scsi", SYSFS{../../../manufacturer}="Tekom Technologies, Inc",
NAME="my_camera"
Frequently the attributes one wants to filter by are spread out
through the tree, especially when they've been subdivided for clarity
as people seem to want to do.
Cheers,
Kyle Moffett
--
I lost interest in "blade servers" when I found they didn't throw
knives at people who weren't supposed to be in your machine room.
-- Anthony de Boer
next prev parent reply other threads:[~2005-11-29 1:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 21:56 Patrick Mochel
2005-11-28 20:49 ` Greg KH
2005-11-29 1:10 ` Kyle Moffett [this message]
2005-11-29 5:44 ` Greg KH
2005-11-29 6:41 ` Kyle Moffett
2005-11-29 6:55 ` Greg KH
2005-11-30 17:05 ` Patrick Mochel
2005-11-30 22:11 ` Greg KH
2005-12-05 6:24 ` Maneesh Soni
2005-12-19 19:08 ` Patrick Mochel
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=37362F2B-D74A-4A40-905B-B25264B6C4AB@mac.com \
--to=mrmacman_g4@mac.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.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
all inboxes | Powered by JetHome®