public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: Marcus Shawcroft <marcus.shawcroft@linaro.org>
Cc: Andreas Jaeger <aj@suse.com>, <libc-ports@sourceware.org>
Subject: Re: [PATCH] AArch64 Indent pre-processor directives.
Date: Tue, 20 Nov 2012 19:28:00 -0000	[thread overview]
Message-ID: <87fw44ysz9.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <CABXK9ncUcXEgfn_bsE224i_agDk7Ptbo6ofmBF4aA0nWoatZ4A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 953 bytes --]

Hi!

On Tue, 20 Nov 2012 12:18:19 +0000, Marcus Shawcroft <marcus.shawcroft@linaro.org> wrote:
> This patch indents the pre-processor directives introduced by this patch:
> 
> http://sourceware.org/ml/libc-ports/2012-11/msg00060.html
> 
> and addresses one of the comments raised by Andreas here:
> 
> http://sourceware.org/ml/libc-ports/2012-11/msg00066.html
> 
> /Marcus
> 
> 2012-11-20  Marcus Shawcroft  <marcus.shawcroft@linaro.org>
> 
>         * sysdeps/aarch64/fpu/s_fma.c: Indent preprocessor directives.
>         * sysdeps/aarch64/fpu/s_fmin.c: Likewise.
>         * sysdeps/aarch64/fpu/s_frint.c: Likewise.
>         * sysdeps/aarch64/fpu/s_frintf.c: Likewise.
>         * sysdeps/aarch64/fpu/s_lrint.c: Likewise.
>         * sysdeps/aarch64/fpu/s_lround.c: Likewise.

Looks good to me, though I have not checked whether there are any further
instances where the indentation should be changed.


Grüße,
 Thomas

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]

      reply	other threads:[~2012-11-20 19:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20 12:18 Marcus Shawcroft
2012-11-20 19:28 ` Thomas Schwinge [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=87fw44ysz9.fsf@kepler.schwinge.homeip.net \
    --to=thomas@codesourcery.com \
    --cc=aj@suse.com \
    --cc=libc-ports@sourceware.org \
    --cc=marcus.shawcroft@linaro.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 read-only IMAP folder(s) and NNTP newsgroup(s).