From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Add MIMC200 board - now uses board_eth_init()
Date: Tue, 29 Jul 2008 18:16:14 -0500 [thread overview]
Message-ID: <488FA4BE.1040307@freescale.com> (raw)
In-Reply-To: <20080729230421.8C5A3248B9@gemini.denx.de>
Wolfgang Denk wrote:
> In message <20080728202251.GA28802@ld0162-tx32.am.freescale.net> you wrote:
>> Aligning with TABs (or at all, in initializer lists) is not a good thing,
>
> It is mandatory per Coding Style requirements.
Where? I don't see any mention of alignment, and while there's no
explicit definition of indentation, the rationale states that the choice
of 8 characters for indentation is "to clearly define where
a block of control starts and ends", which has nothing to do with alignment.
>> IMO -- it screws things up when viewed with any other tab size (and why
>> else have tabs in the first place?).
>
> What do you mean by "other tab size'? See Linux kernel coding style,
> Chapter 1: Indentation:
>
> Tabs are 8 characters, and thus indentations are also 8
> characters.
>
> Tabs are 8 characters. Full stop.
Yes, 8 is the "official" tab size for the Linux and U-Boot projects, for
purposes of line length limits, etc.
That doesn't mean we should go out of our way to screw up alignment when
a different size is used, when it's so easy to avoid. What's the point
of using TAB as a crappy compression scheme, rather than giving it
semantic meaning as the block indentation level?
-Scott
next prev parent reply other threads:[~2008-07-29 23:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 19:32 [U-Boot-Users] [PATCH] Add MIMC200 board - now uses board_eth_init() Mark Jackson
2008-07-28 19:56 ` Ben Warren
2008-07-29 8:52 ` Mark Jackson
2008-07-29 20:06 ` Scott Wood
2008-07-30 9:03 ` Mark Jackson
2008-07-28 20:03 ` Jean-Christophe PLAGNIOL-VILLARD
2008-07-28 20:22 ` Scott Wood
2008-07-29 23:04 ` Wolfgang Denk
2008-07-29 23:16 ` Scott Wood [this message]
2008-07-29 8:26 ` Haavard Skinnemoen
2008-07-29 9:40 ` Mark Jackson
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=488FA4BE.1040307@freescale.com \
--to=scottwood@freescale.com \
--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