From: Greg KH <greg@kroah.com>
To: Kyle Moffett <mrmacman_g4@mac.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 22:55:12 -0800 [thread overview]
Message-ID: <20051129065512.GA4945@kroah.com> (raw)
In-Reply-To: <B43BE39F-16A2-4BFE-A6AA-0F4439780F1C@mac.com>
On Tue, Nov 29, 2005 at 01:41:01AM -0500, Kyle Moffett wrote:
> On Nov 29, 2005, at 00:44, Greg KH wrote:
> >On Mon, Nov 28, 2005 at 08:10:36PM -0500, Kyle Moffett wrote:
> >>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"
> >
> >Why can't you do this today? Have you tried it?
>
> Hmm, no, I don't suppose I have. I guess I was taking the udev docs
> and other similar pages at their word that you couldn't match things
> in multiple subdirs. *tries* Interesting; it appears to work, but
> it would be nice if it was documented somewhere; this is _really_
> handy for certain devices with partial or missing udev support.
Patches for documentation is always gladly accepted :)
> I do have one question, though. Is there any way to access the
> "DEVICE" or "SUBSYSTEM" values of those parent sysfs nodes? I can
> see that those are symlinks in sysfs to other sysfs dirs, so there's
> no real way to match them with SYSFS{*},
As they are symlinks, you might just be able to follow them as part of
the path. But odds are, something in libsysfs would prevent that from
working that way...
thanks,
greg k-h
next prev parent reply other threads:[~2005-11-29 6:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 21:56 [RFC] Updates to sysfs_create_subdir() Patrick Mochel
2005-11-28 20:49 ` Greg KH
2005-11-29 1:10 ` Kyle Moffett
2005-11-29 5:44 ` Greg KH
2005-11-29 6:41 ` Kyle Moffett
2005-11-29 6:55 ` Greg KH [this message]
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=20051129065512.GA4945@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=mrmacman_g4@mac.com \
/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