From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v6 4/4] mpc85xx: Add board support for the eXMeritus HWW-1U-1A devices
Date: Mon, 21 Mar 2011 23:24:03 +0100 [thread overview]
Message-ID: <20110321222403.B1B84CF@gemini.denx.de> (raw)
In-Reply-To: <DDD31591-33CD-49E4-B303-3477E00933BF@boeing.com>
Dear "Moffett, Kyle D",
In message <DDD31591-33CD-49E4-B303-3477E00933BF@boeing.com> you wrote:
>
> I apparently cannot rely on the U-Boot *CODE* to understand what the
> U-Boot *CODING* style is.
You don't have to rely on the code. It's clearly documented.
The README says:
Coding Standards:
-----------------
All contributions to U-Boot should conform to the Linux kernel
coding style; see the file "Documentation/CodingStyle" and the script
"scripts/Lindent" in your Linux kernel source directory...
http://www.denx.de/wiki/U-Boot/CodingStyle says the same.
And the referred document says:
Chapter 2: Breaking long lines and strings
Coding style is all about readability and maintainability using
commonly
available tools.
The limit on the length of lines is 80 columns and this is a strongly
preferred limit.
Statements longer than 80 columns will be broken into sensible chunks.
Now what exactly is unclear here?
And no, you are not the only one who is asked to fix his code beause
of "Line too long" errors. Here just a small collection from the last
4 months or so:
11/11 To:Xiangfu Liu Re: [U-Boot] [PATCH 1/5] those files are jz4740 base files
http://article.gmane.org/gmane.comp.boot-loaders.u-boot/88655
12/04 To:Luigi 'Comio' Re: [U-Boot] [PATCH 5/6 v2] Enable bootstrap support for MIPS architecture.
http://article.gmane.org/gmane.comp.boot-loaders.u-boot/90325
12/12 To:Macpaul Lin Re: [U-Boot] [PATCH] ftgmac100: support of gigabit eth ftgmac100
http://article.gmane.org/gmane.comp.boot-loaders.u-boot/90740
12/12 To:Macpaul Lin Re: [U-Boot] [PATCH] ftgmac100: support of gigabit eth ftgmac100
http://article.gmane.org/gmane.comp.boot-loaders.u-boot/90740
03/13 To:Heiko Schocher Re: [U-Boot] [PATCH 01/20] keymile: rework headerfiles for keymile boards
http://article.gmane.org/gmane.comp.boot-loaders.u-boot/95728
> But otherwise I see no valid reason I should waste any more of my time
> submitting patches which get torn apart out of hand over issues which are
> completely ignored for patches which come in from other maintainers.
This is simply not true. But I'm not sure if you are still listening
to any rational arguments. I can only ask you to calm down, and
eventually reconsider. Sorry.
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
Quote from a recent meeting: "We are going to continue having these
meetings everyday until I find out why no work is getting done."
next prev parent reply other threads:[~2011-03-21 22:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 17:04 [U-Boot] [PATCH v6 0/4] Board support series for the eXMeritus HWW-1U-1A Kyle Moffett
2011-03-15 17:04 ` [U-Boot] [PATCH v6 1/4] mpc8xxx: DDR2/DDR3: Clean up DIMM-type switch statements Kyle Moffett
2011-03-31 8:30 ` Kumar Gala
2011-03-15 17:04 ` [U-Boot] [PATCH v6 2/4] mpc85xx: Add inline GPIO acessor functions Kyle Moffett
2011-03-15 17:04 ` [U-Boot] [PATCH v6 3/4] mpc85xx: Add a board-specific restart hook Kyle Moffett
2011-03-15 19:12 ` Wolfgang Denk
2011-03-15 17:04 ` [U-Boot] [PATCH v6 4/4] mpc85xx: Add board support for the eXMeritus HWW-1U-1A devices Kyle Moffett
2011-03-15 19:36 ` Wolfgang Denk
2011-03-21 16:29 ` Moffett, Kyle D
2011-03-21 20:30 ` Wolfgang Denk
2011-03-21 21:15 ` Moffett, Kyle D
2011-03-21 21:34 ` Wolfgang Denk
2011-03-21 22:01 ` Moffett, Kyle D
2011-03-21 22:24 ` Wolfgang Denk [this message]
2011-03-21 23:07 ` Moffett, Kyle D
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=20110321222403.B1B84CF@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 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.