linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: Vitaly Bordug <vitb@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [Patch] 8xx: MGSUVD support
Date: Mon, 10 Mar 2008 07:33:54 +0100	[thread overview]
Message-ID: <47D4D652.4080902@denx.de> (raw)
In-Reply-To: <20080309195914.69d51e68@kernel.crashing.org>

Hello Vitaly,

Vitaly Bordug wrote:
> Heiko Schocher wrote:
>> the following patch adds support for the MPC852 based mgsuvd board
>> from keymile.
> Looks good overall. Please add supported/working/not working etc SoC devices state along with the patch 
> description. Also a few really small comments below...

OK.

>> Signed-off-by: Heiko Schocher <hs@denx.de>
>> ---
[...]
>> +
>> +		PowerPC,866@0 {
> But it's mpc852, isn't it?

Yes your are right.

>> +			device_type = "cpu";
>> +			reg = <0>;
>> +			d-cache-line-size = <d#16>;
>> +			i-cache-line-size = <d#16>;
>> +			d-cache-size = <d#8192>;
>> +			i-cache-size = <d#8192>;
>> +			timebase-frequency = <0>;  /* Filled in by
>> u-boot */
>> +			bus-frequency = <0>;  /* Filled in by u-boot
>> */
>> +			clock-frequency = <0>; /* Filled in by
>> u-boot */
>> +			interrupts = <f 2>;	// decrementer
>> interrupt
> I would like all the comments to be consistent C style (because that's it for the most other dts'es).

Okay, I fix this, and send a new patch.

bye,
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2008-03-10  6:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-09  9:56 [Patch] 8xx: MGSUVD support Heiko Schocher
2008-03-09 16:59 ` Vitaly Bordug
2008-03-10  6:33   ` Heiko Schocher [this message]
2008-03-17 22:38   ` Scott Wood
2008-03-18  0:27     ` Vitaly Bordug
2008-03-10  3:32 ` Stephen Rothwell
2008-03-10  6:34   ` Heiko Schocher
2008-03-10  6:35     ` Stephen Rothwell

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=47D4D652.4080902@denx.de \
    --to=hs@denx.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=vitb@kernel.crashing.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).