linux-kernel - Re: Platform device id

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070908104041.4d8d1a24@hyperion.delvare>
Date:	Sat, 8 Sep 2007 10:40:41 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Greg KH <gregkh@...e.de>, LKML <linux-kernel@...r.kernel.org>,
	David Brownell <david-b@...bell.net>
Subject: Re: Platform device id

On Fri, 7 Sep 2007 17:56:59 -0300, Henrique de Moraes Holschuh wrote:
> On 9/7/07, Jean Delvare <khali@...ux-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.

-- 
Jean Delvare
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/