From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev - udevinfo with device chain walk
Date: Fri, 23 Jan 2004 03:01:36 +0000 [thread overview]
Message-ID: <20040123030136.GB16893@kroah.com> (raw)
In-Reply-To: <20040123013054.GA2437@vrfy.org>
On Fri, Jan 23, 2004 at 02:30:54AM +0100, Kay Sievers wrote:
> udevinfo is now capable to print "all" attributes along the device chain
> of a sysfs device. Just like udev itself it walks the chain upwards and
> prints all usable attributes in the udev key format.
> So it should be easy to find unique attributes to compose a rule.
>
> All multiline attribute values and values containing non printable
> characters are skipped now. I hope nothing useful gets lost with this :)
>
> NOTE:
> The BUS value corresponding with the attributes is printed for every
> device. Don't specify BUS= in a rule and mix SYSFS_attributes from
> different busses, the rule can't match.
ver nice, applied, thanks.
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-01-23 3:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 1:30 [PATCH] udev - udevinfo with device chain walk Kay Sievers
2004-01-23 3:01 ` Greg KH [this message]
2004-01-23 3:03 ` Greg KH
2004-01-23 4:53 ` Ananth N Mavinakayanahalli
2004-01-23 20:43 ` Greg KH
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=20040123030136.GB16893@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).