From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull u-boot-sparc.git
Date: Thu, 27 May 2010 00:23:19 +0200 [thread overview]
Message-ID: <20100526222319.0DEF7EAC238@gemini.denx.de> (raw)
In-Reply-To: <20100526172855.2w3qpyvp3akgc884@webmail.bluegenesis.com>
Dear daniel at gaisler.com,
In message <20100526172855.2w3qpyvp3akgc884@webmail.bluegenesis.com> you wrote:
> Just a codeing-style question, I have seen other writers of assembly
> code add an extra space before instruction executed in a delay-slot
> (typically after a branch for SPARC) just to make it clear that
> instruction is executed as well. I find that quite good and have
> adopted that habit too, is that allowed?
Ah, that was the meaning. I thought so initially, but then saw a lot
of empty lines separating such blocks, so I assumed it was just
incorrect indentation.
When this is used consistently through all of the code (at least in
the changed files), than it's OK with me.
Ideally it should be documented.
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
After a heated argument on some trivial matter Nancy [Astor] . . .
shouted, ``If I were your wife I would put poison in your coffee!''
Whereupon Winston Churchill with equal heat and sincerity answered,
``And if I were your husband I would drink it.''
next prev parent reply other threads:[~2010-05-26 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 21:28 [U-Boot] Please pull u-boot-sparc.git daniel at gaisler.com
2010-05-26 22:23 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-26 21:20 daniel at gaisler.com
2010-05-26 12:17 Daniel Hellstrom
2010-05-26 21:02 ` 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=20100526222319.0DEF7EAC238@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