From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] TI: DaVinci: GPIO header file and definitions
Date: Wed, 30 Sep 2009 15:56:00 -0500 [thread overview]
Message-ID: <4AC3C5E0.5070904@windriver.com> (raw)
In-Reply-To: <20090930203512.9598D832E408@gemini.denx.de>
Wolfgang Denk wrote:
> Dear Tom,
>
> In message <4AC1FE5C.4070503@windriver.com> you wrote:
>>> +struct davinci_gpio {
>>> + unsigned int dir;
>>> + unsigned int out_data;
>>> + unsigned int set_data;
>>> + unsigned int clr_data;
>>> + unsigned int in_data;
>>> + unsigned int set_rising;
>>> + unsigned int clr_rising;
>>> + unsigned int set_falling;
>>> + unsigned int clr_falling;
>>> + unsigned int intstat;
>>> +};
>> Convert the tabs to spaces in the in the whitespace between
>> type and elemement names
>> unsigned int dir; -> unsigned int dir;
>> For all of the elements
>
> Why? It is not really important here, but especially when mixing data
> types, TABs are preferred, as they will allow for nice vertical
> alignment.
>
OK. TABs are preferred.
The structure defined below it used a single space.
When looked at together, it seemed to me to be inconsistent.
Tom
> Best regards,
>
> Wolfgang Denk
>
next prev parent reply other threads:[~2009-09-30 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 1:29 [U-Boot] [PATCH] TI: DaVinci: GPIO header file and definitions s-paulraj at ti.com
2009-09-29 12:32 ` Tom
2009-09-30 20:35 ` Wolfgang Denk
2009-09-30 20:56 ` Tom [this message]
2009-09-30 21:01 ` Paulraj, Sandeep
2009-09-30 21:47 ` Wolfgang Denk
2009-09-30 21:48 ` Tom
2009-09-30 21:51 ` 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=4AC3C5E0.5070904@windriver.com \
--to=tom.rix@windriver.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