From: Kumar Gala <galak@kernel.crashing.org>
To: Li Yang <leoli@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Convert MPC837x device trees to dts-v1
Date: Fri, 18 Jan 2008 00:31:21 -0600 [thread overview]
Message-ID: <5863BE5F-95D7-499C-AFC4-C7ECE62847D4@kernel.crashing.org> (raw)
In-Reply-To: <1199791957-5309-1-git-send-email-leoli@freescale.com>
On Jan 8, 2008, at 5:32 AM, Li Yang wrote:
> Signed-off-by: Li Yang <leoli@freescale.com>
> ---
> arch/powerpc/boot/dts/mpc8377_mds.dts | 148 +++++++++++++++
> +---------------
> arch/powerpc/boot/dts/mpc8378_mds.dts | 140 ++++++++++++++
> +---------------
> arch/powerpc/boot/dts/mpc8379_mds.dts | 156 ++++++++++++++++
> +----------------
> 3 files changed, 225 insertions(+), 219 deletions(-)
applied.
- k
next prev parent reply other threads:[~2008-01-18 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 11:32 [PATCH] Convert MPC837x device trees to dts-v1 Li Yang
2008-01-18 6:31 ` Kumar Gala [this message]
2008-01-18 6:39 ` 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=5863BE5F-95D7-499C-AFC4-C7ECE62847D4@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=leoli@freescale.com \
--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 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).