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] ppc4xx: Read pipeline depth set to 4 for PPC440SP/SPE, PPC405EX, PPC460EX/GT/SX processors
Date: Wed, 13 Aug 2008 22:01:37 +0200	[thread overview]
Message-ID: <20080813200137.D331D248AC@gemini.denx.de> (raw)
In-Reply-To: <49c0ff980808131204hdc940cel1dcc28d607429f78@mail.gmail.com>

Dear "prodyut hazarika",

In message <49c0ff980808131204hdc940cel1dcc28d607429f78@mail.gmail.com> you wrote:
>
> > > But then, you are changing good TAB chanracters that  were  used  for
> > > vertical  alignment  into spaces. This is incorrect - please read the
> > > Coding Style requirements.
> > >
> > > Please do not do this.
> 
> The problem is that lot of existing code use spaces to align the
> defines. You can see include/ppc4xx.h and lot of other header files. I
> have seen that spaces are used only in defines. As an example in
> ppc4xx.h. I can send thousands of other places.:
> 
> #if defined(CONFIG_405EX) || \$
>     defined(CONFIG_440SP) || defined(CONFIG_440SPE) || \$
>     defined(CONFIG_460EX) || defined(CONFIG_460GT)$
> #define CONFIG_SDRAM_PPC4xx_IBM_DDR2^I/* IBM DDR(2) controller */$
> #endif$

Here it makes sense to align the 'define's vertically, and it seems
obvious that only spaces can be used here.

Yes, I am aware that there are lots of bad examples around, but please
take the good ones as a guide, not the bad ones.

Finally, no matter what any examples were that you might have followed
when writing new code. What I am complaining about is that you changed
good code and converted it into bad one.

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
Quotation, n. The act of repeating erroneously the words of  another.
The  words  erroneously  repeated.
                            - Ambrose Bierce _The Devil's Dictionary_

  parent reply	other threads:[~2008-08-13 20:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13  4:43 [U-Boot] [PATCH] ppc4xx: Read pipeline depth set to 4 for PPC440SP/SPE, PPC405EX, PPC460EX/GT/SX processors fkan at amcc.com
2008-08-13  5:37 ` Wolfgang Denk
2008-08-13  6:26   ` Stefan Roese
2008-08-13  6:44     ` Wolfgang Denk
2008-08-13 13:59     ` Prodyut Hazarika
2008-08-13 14:24       ` Stefan Roese
2008-08-13 17:13   ` Scott Wood
2008-08-13 18:31     ` Wolfgang Denk
2008-08-13 18:44       ` Scott Wood
2008-08-13 19:04   ` prodyut hazarika
2008-08-13 19:16     ` Prodyut Hazarika
2008-08-13 20:08       ` Wolfgang Denk
2008-08-13 20:19         ` Prodyut Hazarika
2008-08-13 20:56           ` Wolfgang Denk
2008-08-13 20:01     ` Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-13 18:10 fkan at amcc.com
2008-08-13 20:10 ` Wolfgang Denk

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=20080813200137.D331D248AC@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