From: David Miller <davem@davemloft.net>
To: dwmw2@infradead.org
Cc: kay.sievers@vrfy.org, md@linux.it, harald@redhat.com,
linux-hotplug@vger.kernel.org, netdev@vger.kernel.org,
schwidefsky@de.ibm.com
Subject: Re: [PATCH] Expose netdevice dev_id through sysfs
Date: Sun, 20 Apr 2008 03:55:15 -0700 (PDT) [thread overview]
Message-ID: <20080420.035515.12616544.davem@davemloft.net> (raw)
In-Reply-To: <1208688644.9212.407.camel@pmac.infradead.org>
From: David Woodhouse <dwmw2@infradead.org>
Date: Sun, 20 Apr 2008 11:50:44 +0100
> Certainly, it's possible that we'll need _more_ criteria for udev to
> match on; that doesn't necessarily mean that dev_id shouldn't be one of
> them, does it?
I've read what you have to say, and your point is logical.
However you've just also stated that dev_id isn't even needed to solve
the particular problems you're interested in.
I'm not against exporting the value. But let's do it because it does
solve a problem, not because it's fun to export every object instance
variable via sysfs :-)
next prev parent reply other threads:[~2008-04-20 10:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ftdb3v$tls$1@ger.gmane.org>
[not found] ` <20080407143805.GA9492@bongo.bofh.it>
2008-04-14 10:08 ` udev can't name PS3's network devices correctly David Woodhouse
2008-04-14 11:11 ` David Woodhouse
2008-04-14 11:55 ` Kay Sievers
2008-04-14 12:32 ` [PATCH] Expose netdevice dev_id through sysfs David Woodhouse
2008-04-20 1:33 ` David Miller
2008-04-20 5:21 ` Andrey Borzenkov
2008-04-20 5:32 ` David Miller
2008-04-20 10:50 ` David Woodhouse
2008-04-20 10:55 ` David Miller [this message]
2008-04-20 11:12 ` David Woodhouse
2008-04-20 11:14 ` David Miller
2008-04-20 11:22 ` David Woodhouse
2008-04-27 17:37 ` udev can't name PS3's network devices correctly David Woodhouse
2008-04-27 18:28 ` Kay Sievers
2008-04-14 12:03 ` Kay Sievers
2008-04-14 12:19 ` David Woodhouse
2008-04-14 12:52 ` Kay Sievers
2008-04-14 13:16 ` David Woodhouse
2008-04-14 12:51 ` Marco d'Itri
2008-04-14 13:38 ` David Woodhouse
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=20080420.035515.12616544.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=harald@redhat.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
--cc=md@linux.it \
--cc=netdev@vger.kernel.org \
--cc=schwidefsky@de.ibm.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;
as well as URLs for NNTP newsgroup(s).