From: Segher Boessenkool <segher@kernel.crashing.org>
To: David Gibson <dwg@au1.ibm.com>
Cc: Alexandre Bounine <Alexandre.Bounine@tundra.com>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: Fix problems with device tree representation of TSI-1xx bridges
Date: Wed, 30 May 2007 15:28:24 +0200 [thread overview]
Message-ID: <9db95465199af5090a48726476677a2a@kernel.crashing.org> (raw)
In-Reply-To: <20070530013718.GB21955@localhost.localdomain>
> This patch fixes some problems with the way the some things
> represented in the device tree for the Holly and Taiga boards. This
> means changes both to the dts files, and to the code which
> instantiates the tsi108 ethernet platform devices based on the device
> tree.
Looks fine now :-)
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Acked-by: Segher Boessenkool <segher@kernel.crashing.org>
Segher
next prev parent reply other threads:[~2007-05-30 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 1:37 Fix problems with device tree representation of TSI-1xx bridges David Gibson
2007-05-30 13:28 ` Segher Boessenkool [this message]
2007-05-30 13:44 ` Josh Boyer
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=9db95465199af5090a48726476677a2a@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=Alexandre.Bounine@tundra.com \
--cc=dwg@au1.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).