From: Szabolcs Nagy <Szabolcs.Nagy@arm.com>
To: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>,
Rogerio Alves <rcardoso@linux.ibm.com>,
"Gabriel F. T. Gomes" <gabriel@inconstante.eti.br>
Cc: nd <nd@arm.com>, Florian Weimer <fweimer@redhat.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [PATCH] power: Fix VSCR position on ucontext
Date: Fri, 11 Jan 2019 12:01:00 -0000 [thread overview]
Message-ID: <fdc2922b-e130-623a-bbc4-757d2aeba90c@arm.com> (raw)
In-Reply-To: <87k1jc5lzs.fsf@linux.ibm.com>
On 10/01/2019 19:52, Tulio Magno Quites Machado Filho wrote:
>> /* This test is supported only on POWER 5 or higher. */
>> +#define PPC_CPU_SUPPORTED (PPC_FEATURE_POWER5 | PPC_FEATURE_POWER5_PLUS | \
>> + PPC_FEATURE_ARCH_2_05 | PPC_FEATURE_ARCH_2_06 | \
>
> The GNU Coding Standard requires to replace 8 spaces with a tab.
> Fixed locally. ;-)
there was a discussion recently, that actually it does not
require such thing (it's just an unfortunate default in
emacs which makes the code unreadable in any way other than
8 space == 1 tab, also breaks patch review and email replies,
but we have to format this way for the sake of emacs users
who otherwise would mess up white space formatting).
next prev parent reply other threads:[~2019-01-11 12:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 16:14 Rogerio Alves
2018-11-14 18:00 ` Florian Weimer
2018-11-16 13:18 ` Gabriel F. T. Gomes
2018-12-07 18:28 ` Rogerio Alves
2018-12-07 19:23 ` Gabriel F. T. Gomes
2018-12-10 17:18 ` Tulio Magno Quites Machado Filho
2018-12-10 18:12 ` Gabriel F. T. Gomes
2018-12-10 18:08 ` Gabriel F. T. Gomes
2018-12-10 18:25 ` Rogerio Alves
2018-12-10 21:20 ` Tulio Magno Quites Machado Filho
2018-12-19 19:30 ` Rogerio Alves
2019-01-10 19:52 ` Tulio Magno Quites Machado Filho
2019-01-11 12:01 ` Szabolcs Nagy [this message]
2019-01-11 12:15 ` Tulio Magno Quites Machado Filho
2019-01-11 19:52 ` Tulio Magno Quites Machado Filho
2019-01-11 23:49 ` Joseph Myers
2019-01-12 0:50 ` Tulio Magno Quites Machado Filho
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=fdc2922b-e130-623a-bbc4-757d2aeba90c@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=fweimer@redhat.com \
--cc=gabriel@inconstante.eti.br \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=rcardoso@linux.ibm.com \
--cc=tuliom@ascii.art.br \
/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).