From: "Raf D'Halleweyn" <list@noduck.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] conditional remove of trailing sysfs whitespace
Date: Thu, 04 Mar 2004 20:05:27 +0000 [thread overview]
Message-ID: <1078430727.26549.1.camel@base> (raw)
In-Reply-To: <20040304124223.GA16249@vrfy.org>
Except if you have two devices with "Vendor" and "Vendor "...
Raf.
On Thu, 2004-03-04 at 14:03, Greg KH wrote:
> On Thu, Mar 04, 2004 at 01:42:23PM +0100, Kay Sievers wrote:
> > Hey, it may never happen, that one wants to distinguish attributes by
> > trailing spaces, but we should not lose the control over it, just for
> > being lazy :)
> >
> > Here we remove the trailing spaces of the sysfs attribute only if the
> > configured value to match doesn't have any trailing spaces by itself.
> > So if you put a attribute in a rule with spaces at the end, the sysfs
> > attribute _must_ match exactly.
> >
> > Is that cool for everyone?
> >
> > As usual, 2 tests are added for it with a artificial sysfs file and
> > a few words to the man page.
>
> Very nice solution. This should make everyone happen, as it will "just
> work" for whatever people want it to do, no config option needed.
>
> thanks so much,
>
> greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
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-03-04 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 12:42 [PATCH] conditional remove of trailing sysfs whitespace Kay Sievers
2004-03-04 17:07 ` Richard Troth
2004-03-04 19:03 ` Greg KH
2004-03-04 20:05 ` Raf D'Halleweyn [this message]
2004-03-04 20:11 ` 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=1078430727.26549.1.camel@base \
--to=list@noduck.net \
--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).