From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ulpi: add generic ULPI support header file
Date: Wed, 02 Nov 2011 16:19:51 +0200 [thread overview]
Message-ID: <4EB15187.1050804@compulab.co.il> (raw)
In-Reply-To: <20111102133827.D33F816F8444@gemini.denx.de>
On 11/02/11 15:38, Wolfgang Denk wrote:
> Dear Igor Grinberg,
>
> In message <4EB110D3.5020400@compulab.co.il> you wrote:
>>
>> In the structure above, you have a mixture of tab and spaces
>> after the type before the name.
>> You can use either tabs or spaces (I prefer spaces), but not both.
>
> http://www.denx.de/wiki/U-Boot/CodingStyle states clearly:
>
> Use TAB characters for indentation and vertical alignment, not
> spaces.
Of course not spaces, Wolfgang, you've misunderstood what I said.
It is one space for one line, see the example below.
That's how it looks currently:
struct something {
type var1;
type var2;
type var3;
type var4;
};
What I mean is either of two:
struct something {
type var1;
type var2;
type var3;
type var3;
};
or
struct something {
type var1;
type var2;
type var3;
type var3;
};
The second is motivated by absence of an alignment issue,
because the type is always the same (u8).
Now, if the type is different among fields, then of course tab(s)
should be used for alignment!
Hope now we are talking the same thing.
--
Regards,
Igor.
next prev parent reply other threads:[~2011-11-02 14:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 19:12 [U-Boot] [PATCH] ulpi: add generic ULPI support header file Jana Rapava
2011-11-02 9:43 ` Igor Grinberg
2011-11-02 10:24 ` Marek Vasut
2011-11-02 13:38 ` Wolfgang Denk
2011-11-02 14:19 ` Igor Grinberg [this message]
2011-11-02 18:42 ` [U-Boot] [PATCH v2] " Jana Rapava
2011-11-03 7:08 ` Igor Grinberg
2011-11-08 10:52 ` Igor Grinberg
2011-11-12 17:17 ` [U-Boot] [PATCH v3] " Jana Rapava
2011-11-14 8:01 ` Igor Grinberg
2011-11-14 8:22 ` Igor Grinberg
2011-11-14 19:06 ` Jana Rapava
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=4EB15187.1050804@compulab.co.il \
--to=grinberg@compulab.co.il \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.