From: Martyn Welch <martyn.welch@gefanuc.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org
Subject: Re: [PATCH 2/2] powerpc/86xx: Add new LAW & MCM device tree nodes for all 86xx systems
Date: Tue, 28 Apr 2009 10:19:50 +0100 [thread overview]
Message-ID: <49F6CA36.3040403@gefanuc.com> (raw)
In-Reply-To: <1240855188-24879-2-git-send-email-galak@kernel.crashing.org>
Kumar Gala wrote:
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> ---
> arch/powerpc/boot/dts/gef_ppc9a.dts | 13 +++++++++++++
> arch/powerpc/boot/dts/gef_sbc310.dts | 13 +++++++++++++
> arch/powerpc/boot/dts/gef_sbc610.dts | 13 +++++++++++++
> arch/powerpc/boot/dts/mpc8610_hpcd.dts | 13 +++++++++++++
> arch/powerpc/boot/dts/mpc8641_hpcn.dts | 13 +++++++++++++
> arch/powerpc/boot/dts/mpc8641_hpcn_36b.dts | 13 +++++++++++++
> arch/powerpc/boot/dts/sbc8641d.dts | 13 +++++++++++++
> 7 files changed, 91 insertions(+), 0 deletions(-)
>
Am I right in thinking that this patch doesn't (as yet) enable any added
functionality, or have I missed something?
I assume this is destined for next (as it relies on Becky's
"powerpc/86xx: Add 36-bit device tree for mpc8641hpcn"), assuming this,
fwiw, seems good to me.
Martyn
--
Martyn Welch MEng MPhil MIET (Principal Software Engineer) T:+44(0)1327322748
GE Fanuc Intelligent Platforms Ltd, |Registered in England and Wales
Tove Valley Business Park, Towcester, |(3828642) at 100 Barbirolli Square,
Northants, NN12 6PF, UK T:+44(0)1327359444 |Manchester,M2 3AB VAT:GB 927559189
prev parent reply other threads:[~2009-04-28 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 17:59 [PATCH 1/2] powerpc/86xx: Add binding for LAWs and MCM Kumar Gala
2009-04-27 17:59 ` Kumar Gala
2009-04-27 17:59 ` [PATCH 2/2] powerpc/86xx: Add new LAW & MCM device tree nodes for all 86xx systems Kumar Gala
2009-04-28 9:19 ` Martyn Welch [this message]
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=49F6CA36.3040403@gefanuc.com \
--to=martyn.welch@gefanuc.com \
--cc=devicetree-discuss@ozlabs.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.