From: Scott James Remnant <scott@canonical.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Patches for device names
Date: Wed, 13 Aug 2008 18:02:58 +0000 [thread overview]
Message-ID: <1218650578.6882.67.camel@quest> (raw)
In-Reply-To: <1218648175.6882.63.camel@quest>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
On Wed, 2008-08-13 at 10:50 -0700, Greg KH wrote:
> On Wed, Aug 13, 2008 at 06:22:55PM +0100, Scott James Remnant wrote:
> > Before I get patching, I wanted to get a consensus about what the best
> > patches would be, since there's a few options:
>
> Wait, why do this at all?
>
> To get rid of a few udev rules that group things into subdirectories?
>
> Is that really a sane/wise/useful thing to do? Is your goal to get rid
> of _all_ udev rules by doing this? If not, then why worry about it?
>
To get rid of all udev rules that set a NAME based only on information
received from the kernel.
Why waste cycles and resources constructing a static name just because
the kernel's static name doesn't match the standard?
Scott
--
Scott James Remnant
scott@canonical.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-08-13 18:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 17:22 Patches for device names Scott James Remnant
2008-08-13 17:31 ` H. Peter Anvin
2008-08-13 17:49 ` Greg KH
2008-08-13 17:50 ` Greg KH
2008-08-13 17:57 ` Scott James Remnant
2008-08-13 18:02 ` Scott James Remnant [this message]
2008-08-13 18:16 ` Greg KH
2008-08-13 18:22 ` H. Peter Anvin
2008-08-13 18:33 ` Scott James Remnant
2008-08-13 18:38 ` David Zeuthen
2008-08-13 18:52 ` Kay Sievers
2008-08-13 18:54 ` Kay Sievers
2008-08-13 19:33 ` Scott James Remnant
2008-08-13 20:00 ` H. Peter Anvin
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=1218650578.6882.67.camel@quest \
--to=scott@canonical.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 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.