public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc/85xx: Add basic support for P1023RDS board
Date: Wed, 08 Jun 2011 11:34:46 +0200	[thread overview]
Message-ID: <20110608093446.85A331E9FDF@gemini.denx.de> (raw)
In-Reply-To: <2239AC579C7D3646A720227A37E0268115768A@039-SN1MPN1-004.039d.mgd.msft.net>

Dear Zang Roy-R61911,


[excessive Cc: list trimmed]

In message <2239AC579C7D3646A720227A37E0268115768A@039-SN1MPN1-004.039d.mgd.msft.net> you wrote:
> 
> > Please fix the checkpatch warnings (7 lines over 80 characters)
> 
> I can fix it. In fact, I use checkpatch every time before I send out patch.

Then I do not understand why you submitted the patch at all before
cleaning it up.

> If you check the board header file, most of them has this problem.

Cleanup patches are welcome.

> Do you think 
> + /* physical addr of CCSRBAR */
> +#define CONFIG_SYS_CCSRBAR_PHYS        CONFIG_SYS_CCSRBAR
> is better than
> +#define CONFIG_SYS_CCSRBAR_PHYS        CONFIG_SYS_CCSRBAR      /* physical
>  addr of CCSRBAR */
> ???
> Please clarify.

At least the first version does not violate coding style requirements.

Regarding the general topic of comments - there are such and such
comments.  Things like

	i = i + 1;	/* Increment variable i by one */

are gratuitous and of no use at all.

In your example above, I ask myself why we need
CONFIG_SYS_CCSRBAR_PHYS at all when whe already have
CONFIG_SYS_CCSRBAR (or vice versa).

And why we need a comment that explains this in grat detail - separate
for each single macro.

Please re-read "Chapter 8: Commenting" in the coding-style document
for more details.


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The philosophy exam was a piece of cake  -  which  was  a  bit  of  a
surprise, actually, because I was expecting some questions on a sheet
of paper.

      reply	other threads:[~2011-06-08  9:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08  4:51 [U-Boot] [PATCH] powerpc/85xx: Add basic support for P1023RDS board Roy Zang
2011-06-08  5:30 ` Wolfgang Denk
2011-06-08  5:45   ` Zang Roy-R61911
2011-06-08  9:34     ` Wolfgang Denk [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=20110608093446.85A331E9FDF@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /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