From: Segher Boessenkool <segher@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@ozlabs.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] add Phytec pcm030 board support
Date: Tue, 6 May 2008 07:51:55 +0200 [thread overview]
Message-ID: <4df1ef3575f95f1daf2d67e237ead667@kernel.crashing.org> (raw)
In-Reply-To: <20080506140656.7cff910c.sfr@canb.auug.org.au>
>> PowerPC? check.
>> Sparc? check.
>> Microblaze? check.
>
> OLPC? check?
No check. The kernel hardly uses the device tree at all, there.
Segher
next prev parent reply other threads:[~2008-05-06 5:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 13:48 [PATCH] add Phytec pcm030 board support Sascha Hauer
2008-05-05 1:16 ` David Gibson
2008-05-05 15:59 ` Grant Likely
2008-05-05 18:06 ` Segher Boessenkool
2008-05-05 19:38 ` Grant Likely
2008-05-06 4:06 ` Stephen Rothwell
2008-05-06 5:51 ` Segher Boessenkool [this message]
2008-05-06 7:20 ` Stephen Rothwell
2008-05-05 17:01 ` Jon Smirl
2008-05-05 17:08 ` Grant Likely
2008-05-05 17:22 ` Jon Smirl
2008-05-06 8:08 ` Sascha Hauer
2008-05-06 12:47 ` Jon Smirl
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=4df1ef3575f95f1daf2d67e237ead667@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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).