From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] ARM cleanups
Date: Mon, 17 Nov 2014 20:29:11 +0000 [thread overview]
Message-ID: <20141117202911.GZ4042@n2100.arm.linux.org.uk> (raw)
The following series is partly a result of reviewing differences
between ARM and ARM64, and cleans up ARM with some of the changes
made to ARM64. Many of these changes are trivial cleanups.
I've also dropped some of the kernel boot messages - removing the
"SMP: Total of %d processors activated" message which was redundant,
and dropping a couple of others to debug level.
I've moved the ftrace assembly code to its own separate file, just
like on ARM64.
I've been running stuff with this for a number of weeks now, and
haven't noticed any regressions.
arch/arm/common/sa1111.c | 13 +--
arch/arm/kernel/Makefile | 1 +
arch/arm/kernel/atags_compat.c | 6 +-
arch/arm/kernel/atags_parse.c | 5 +-
arch/arm/kernel/atags_proc.c | 4 +-
arch/arm/kernel/bios32.c | 2 +-
arch/arm/kernel/dma-isa.c | 4 +-
arch/arm/kernel/dma.c | 26 ++---
arch/arm/kernel/entry-common.S | 235 --------------------------------------
arch/arm/kernel/entry-ftrace.S | 243 ++++++++++++++++++++++++++++++++++++++++
arch/arm/kernel/etm.c | 12 +-
arch/arm/kernel/fiq.c | 2 +-
arch/arm/kernel/io.c | 5 +-
arch/arm/kernel/irq.c | 8 +-
arch/arm/kernel/machine_kexec.c | 6 +-
arch/arm/kernel/module.c | 2 +-
arch/arm/kernel/setup.c | 1 +
arch/arm/kernel/smp.c | 15 +--
arch/arm/kernel/smp_twd.c | 4 +-
arch/arm/kernel/swp_emulate.c | 2 +-
arch/arm/kernel/thumbee.c | 2 +-
arch/arm/kernel/topology.c | 4 +-
arch/arm/kernel/traps.c | 42 +++----
arch/arm/kernel/xscale-cp0.c | 7 +-
arch/arm/mm/alignment.c | 10 +-
arch/arm/mm/cache-feroceon-l2.c | 6 +-
arch/arm/mm/cache-tauros2.c | 12 +-
arch/arm/mm/fault-armv.c | 6 +-
arch/arm/mm/fault.c | 31 +++--
arch/arm/mm/init.c | 4 +-
arch/arm/mm/mmu.c | 38 +++----
arch/arm/nwfpe/fpmodule.c | 8 +-
arch/arm/vfp/vfpsingle.c | 2 +-
33 files changed, 378 insertions(+), 390 deletions(-)
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
next reply other threads:[~2014-11-17 20:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 20:29 Russell King - ARM Linux [this message]
2014-11-17 20:29 ` [PATCH 1/8] ARM: convert printk(KERN_* to pr_* Russell King
2014-11-19 2:02 ` Andrew Lunn
2014-11-17 20:29 ` [PATCH 2/8] ARM: use pr_warn_ratelimited() when migrating IRQs Russell King
2014-11-17 20:29 ` [PATCH 3/8] ARM: drop nwfpe initialisation message from warning to info level Russell King
2014-11-17 20:30 ` [PATCH 4/8] ARM: reduce "Booted secondary processor" message to debug level Russell King
2014-11-17 20:30 ` [PATCH 5/8] ARM: remove "SMP: Total of %d processors activated." message Russell King
2014-11-17 20:30 ` [PATCH 6/8] ARM: add machine name to stack dump output Russell King
2014-11-19 2:29 ` Stephen Boyd
2014-11-17 20:30 ` [PATCH 7/8] ARM: move ftrace assembly code to separate file Russell King
2014-11-17 20:30 ` [PATCH 8/8] ARM: io.c: clean up EXPORT_SYMBOL()s Russell King
2014-11-17 23:16 ` [PATCH 0/8] ARM cleanups Felipe Balbi
2014-11-20 19:37 ` Felipe Balbi
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=20141117202911.GZ4042@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).