From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Jean Delvare <khali@linux-fr.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Greg KH <gregkh@suse.de>, LKML <linux-kernel@vger.kernel.org>,
David Brownell <david-b@pacbell.net>
Subject: Re: Platform device id
Date: Mon, 10 Sep 2007 19:45:38 -0300 [thread overview]
Message-ID: <20070910224537.GA1408@khazad-dum.debian.net> (raw)
In-Reply-To: <20070908104041.4d8d1a24@hyperion.delvare>
On Sat, 08 Sep 2007, Jean Delvare wrote:
> On Fri, 7 Sep 2007 17:56:59 -0300, Henrique de Moraes Holschuh wrote:
> > On 9/7/07, Jean Delvare <khali@linux-fr.org> wrote:
> > > To go one step further, I am questioning the real value of this naming
> > > exception for these "unique" platform devices. On top of the bugs I
> > > mentioned above, it has potential for compatibility breakage: adding a
> >
> > Agreed. But the breakage might happen anyway, if you need to move
> > attributes from foo.0 to foo.1. After that first time, userspace will learn
> > to hunt down all foo.* after what it wants, but still...
>
> Moving attributes from one device to another? This doesn't make any
> sense to me, sorry. foo.0 and foo.1 represent different instances of
> the same device type, they typically have the same attributes.
Yeah, I came across that need in an attempt to fix an issue in thinkpad-acpi
which will be fixed in another way (separate modules, or separate platform
devices/platform drivers in the same module). I must have been
sleep-deprieved and in a weird mind state of sorts (and not in a nice way)
to come up with it.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2007-09-10 22:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 13:35 Jean Delvare
2007-09-07 14:58 ` Dmitry Torokhov
2007-09-07 16:36 ` Jean Delvare
2007-09-07 16:41 ` David Brownell
2007-09-07 21:00 ` Henrique de Moraes Holschuh
2007-09-07 21:41 ` David Brownell
2007-09-07 22:04 ` Henrique de Moraes Holschuh
2007-09-08 0:18 ` David Brownell
2007-09-08 3:50 ` Henrique de Moraes Holschuh
2007-09-08 8:55 ` Jean Delvare
2007-09-10 22:52 ` Henrique de Moraes Holschuh
2007-09-11 7:43 ` Jean Delvare
2007-09-11 13:44 ` Henrique de Moraes Holschuh
2007-09-11 14:05 ` Jean Delvare
2007-09-07 20:56 ` Henrique de Moraes Holschuh
2007-09-08 8:40 ` Jean Delvare
2007-09-10 22:45 ` Henrique de Moraes Holschuh [this message]
2007-09-08 13:30 ` Greg KH
2007-09-09 10:54 ` [PATCH] Make platform_device.id an int Jean Delvare
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=20070910224537.GA1408@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=david-b@pacbell.net \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@suse.de \
--cc=khali@linux-fr.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®