From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Patches for device names
Date: Wed, 13 Aug 2008 18:22:35 +0000 [thread overview]
Message-ID: <48A3266B.1040201@zytor.com> (raw)
In-Reply-To: <1218648175.6882.63.camel@quest>
Greg KH wrote:
>
> So the kernel should cache this information? That's a mess, why do that
> when userspace already has this mapping (udevinfo provides it). We
> already have a mapping from device major/minor already in sysfs as well.
>
> So why would the kernel need to care about this?
>
Fair enough.
Now, calling udevinfo is quite expensive; is this information available
through a programmatic API?
-hpa
next prev parent reply other threads:[~2008-08-13 18:22 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
2008-08-13 18:16 ` Greg KH
2008-08-13 18:22 ` H. Peter Anvin [this message]
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=48A3266B.1040201@zytor.com \
--to=hpa@zytor.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).