From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: bus_id collisions
Date: Tue, 21 Nov 2006 17:49:20 +1100 [thread overview]
Message-ID: <1164091760.5597.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20061121064122.GA10510@kroah.com>
> Oh, that's a very annoying bus id, but I guess it's legal.
>
> I'll poke around and see if I can make it bigger. You don't want it
> bigger for static 'struct device' types, right?
Don't bother too much if it's complicated. I'm trying other options as
well, like possibly using the Open Firmware "phandle" (sort of object
ID) which is only 32 bits, provided I can get the embedded folks to
agree to have one at all...
Cheers,
Ben.
next prev parent reply other threads:[~2006-11-21 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 4:02 bus_id collisions Benjamin Herrenschmidt
2006-11-21 6:13 ` David Miller
2006-11-21 6:23 ` Benjamin Herrenschmidt
2006-11-21 6:41 ` Greg KH
2006-11-21 6:49 ` Benjamin Herrenschmidt [this message]
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=1164091760.5597.18.camel@localhost.localdomain \
--to=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