From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: patches@linaro.org
Subject: [Qemu-devel] [PATCH 0/3] Detabify target/arm
Date: Tue, 21 Aug 2018 17:52:12 +0100 [thread overview]
Message-ID: <20180821165215.29069-1-peter.maydell@linaro.org> (raw)
This patchset removes hardcoded tabs from target/arm.
Normally we're generally against patches which only do style
fixups, preferring to fix up code as we need to touch it.
But in this case, almost all of the tabs are in the old
iwMMXt instruction set handling, which we have not needed
to touch in years, so the "fix as we touch it" process isn't
going to adjust them. Also, since they're changes to
barely-touched code they're not going to cause conflicts with
other work-in-progress in that area or be likely to result in
future pain trying to do stable backports of bugfixes.
So I think it's reasonable to do a bulk fixup in this case,
especially for translate.c, which is a file that sees active
development in other parts of the same file.
This isn't intended to announce an open season for
coding style fixup patches -- that is up to the individual
submaintainer and should not be done unsolicited.
thanks
-- PMM
Peter Maydell (3):
target/arm: Untabify translate.c
target/arm: Untabify iwmmxt_helper.c
target/arm: Remove a handful of stray tabs
target/arm/cpu.h | 16 +--
target/arm/arm-semi.c | 2 +-
target/arm/iwmmxt_helper.c | 234 ++++++++++++++++++-------------------
target/arm/translate.c | 122 +++++++++----------
4 files changed, 187 insertions(+), 187 deletions(-)
--
2.18.0
next reply other threads:[~2018-08-21 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 16:52 Peter Maydell [this message]
2018-08-21 16:52 ` [Qemu-devel] [PATCH 1/3] target/arm: Untabify translate.c Peter Maydell
2018-08-21 16:52 ` [Qemu-devel] [PATCH 2/3] target/arm: Untabify iwmmxt_helper.c Peter Maydell
2018-08-21 16:52 ` [Qemu-devel] [PATCH 3/3] target/arm: Remove a handful of stray tabs Peter Maydell
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=20180821165215.29069-1-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=patches@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).