From: Johannes Berg <johannes@sipsolutions.net>
To: Michael Ellerman <michaelellerman@internode.on.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] PowerMac11,2 i2c-bus@0 duplicate dev-tree workaround
Date: Fri, 31 Mar 2006 00:38:17 +0200 [thread overview]
Message-ID: <1143758297.5388.12.camel@localhost> (raw)
In-Reply-To: <1143700119.23392.27.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
On Thu, 2006-03-30 at 17:28 +1100, Michael Ellerman wrote:
> I don't understand why we need this patch? If we care about getting the
> "right" node why not check for that where we care?
It's not just a single node but also contains sub-nodes. In one of them,
one of those sub nodes is there but contains bogus info, and in the
other both are there and contain the right info. Some things that work
off these bus nodes are detected twice if they're there, and they're
used in at least two places that I know of.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
next prev parent reply other threads:[~2006-03-30 22:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 11:30 [PATCH] PowerMac11,2 i2c-bus@0 duplicate dev-tree workaround Johannes Berg
2006-03-30 4:26 ` Benjamin Herrenschmidt
2006-03-30 13:04 ` Johannes Berg
2006-03-30 6:28 ` Michael Ellerman
2006-03-30 22:38 ` Johannes Berg [this message]
2006-03-31 5:37 ` Michael Ellerman
2006-03-31 9:42 ` Johannes Berg
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=1143758297.5388.12.camel@localhost \
--to=johannes@sipsolutions.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=michaelellerman@internode.on.net \
/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;
as well as URLs for NNTP newsgroup(s).