Date: Mon, 20 Nov 2006 22:13:29 -0800 (PST)
Message-Id: <20061120.221329.74747650.davem@davemloft.net>
To: benh@kernel.crashing.org
Cc: greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: bus_id collisions
From: David Miller <davem@davemloft.net>
In-Reply-To: <1164081736.8207.14.camel@localhost.localdomain>
References: <1164081736.8207.14.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 804
Lines: 18

From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Tue, 21 Nov 2006 15:02:16 +1100

> This has caused me some trouble with of_platform devices, which are
> sort-of platform devices but linked to the Open Firmware device-tree, as
> I generate their names based on the nodes in the tree which need not be
> unique as long as they are unique under a given parent.
> 
> I've worked around it, but I though the comment might need to be
> clarified.

BTW Ben, on sparc64 for of devices I use "%08x" and the PROM
node ID as the bus_id[] to deal with this.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/