From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] cmd_mem.c: Fix simple typoes, no functional changes.
Date: Sun, 03 Feb 2013 13:14:33 +0100 [thread overview]
Message-ID: <20130203121433.79E6620040A@gemini.denx.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1302030522480.6448@oneiric>
Dear Robert,
In message <alpine.DEB.2.02.1302030522480.6448@oneiric> you wrote:
>
> so what is the actual standard? besides the above, line space
> above? line space below? because i see all sorts of variations in
> the code, the most common of which is:
The "standard" is the Linux CodingStyle:
------------------------- snip ----------------------
The preferred style for long (multi-line) comments is:
/*
* This is the preferred style for multi-line
* comments in the Linux kernel source code.
* Please use it consistently.
*
* Description: A column of asterisks on the left side,
* with beginning and ending almost-blank lines.
*/
------------------------- snip ----------------------
Regarding the space above and blow, I'm not aware of any "standard".
Please apply common sense.
> which, as you can see, has a leading blank line but not a following
> one. so what's correct? is this written down somewhere?
Not that I'm aware of.
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
A year spent in artificial intelligence is enough to make one believe
in God.
prev parent reply other threads:[~2013-02-03 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 16:04 [U-Boot] [PATCH] cmd_mem.c: Fix simple typoes, no functional changes Robert P. J. Day
2013-02-02 19:23 ` Jeroen Hofstee
2013-02-03 9:08 ` Robert P. J. Day
2013-02-03 10:16 ` Wolfgang Denk
2013-02-03 10:23 ` Robert P. J. Day
2013-02-03 12:14 ` 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=20130203121433.79E6620040A@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