From: David Miller <davem@davemloft.net>
To: benh@kernel.crashing.org
Cc: greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: bus_id collisions
Date: Mon, 20 Nov 2006 22:13:29 -0800 (PST) [thread overview]
Message-ID: <20061120.221329.74747650.davem@davemloft.net> (raw)
In-Reply-To: <1164081736.8207.14.camel@localhost.localdomain>
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.
next prev parent reply other threads:[~2006-11-21 6:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 4:02 Benjamin Herrenschmidt
2006-11-21 6:13 ` David Miller [this message]
2006-11-21 6:23 ` Benjamin Herrenschmidt
2006-11-21 6:41 ` Greg KH
2006-11-21 6:49 ` Benjamin Herrenschmidt
2006-11-22 4:38 ` Kumar Gala
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=20061120.221329.74747650.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=benh@kernel.crashing.org \
--cc=greg@kroah.com \
--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®