From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: Tom Rini <trini@kernel.crashing.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>,
ML linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: ASM formatting rules?
Date: Tue, 29 Mar 2005 08:21:50 +1000 [thread overview]
Message-ID: <1112048510.5410.60.camel@gaston> (raw)
In-Reply-To: <ffec644f8c4f3bc32922882631c0da3e@freescale.com>
On Mon, 2005-03-28 at 10:44 -0600, Kumar Gala wrote:
> Guys,
>
> While this is not overly important to me, I was wondering if we had any
> rules related to formatting of assembly files. We seem to have code
> formatted with and without spaces in the args.
>
> I'm assuming something like this (w/o spaces):
>
> <TAB>insn<TAB>argD,arg1,arg2
>
> is what we want? Just trying to get a rule documented going forward.
I used to have argD, arg1, arg2 but since everything else was "compact",
I now tend to adapt to everything else ;)
Ben.
next prev parent reply other threads:[~2005-03-28 22:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 16:44 ASM formatting rules? Kumar Gala
2005-03-28 16:56 ` Tom Rini
2005-03-28 17:11 ` Dan Malek
2005-03-28 17:22 ` Matt Porter
2005-03-28 21:37 ` Paul Mackerras
2005-03-28 23:07 ` Kumar Gala
2005-04-04 6:33 ` Paul Mackerras
2005-04-05 16:45 ` Dan Malek
2005-03-28 22:21 ` Benjamin Herrenschmidt [this message]
2005-03-29 8:32 ` Gabriel Paubert
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=1112048510.5410.60.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=paulus@samba.org \
--cc=trini@kernel.crashing.org \
/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;
as well as URLs for NNTP newsgroup(s).