From: computersforpeace@gmail.com (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] ARM: move #include <asm/cp15.h> into cacheflush.h
Date: Mon, 29 Sep 2014 18:35:25 -0700 [thread overview]
Message-ID: <1412040930-16864-1-git-send-email-computersforpeace@gmail.com> (raw)
There are several places where an explicit include of <asm/cp15.h> is needed
just because cacheflush.h uses one of its macros in v7_exit_coherency_flush().
Let's put the include in the proper header.
These obviously have some dependencies, so I'd focus on:
(1) Is patch 1 acceptable? If so, then:
(2) Make sure patch 1 is serialized before the rest
I did a cursory scan of every file that includes cp15.h, and these are the only
ones I found that only needed it for the sake of v7_exit_coherency_flush().
These are barely compile tested.
Thanks,
Brian
Brian Norris (5):
ARM: include missing cp15.h header
ARM: mvebu: drop unnecessary include
ARM: rockchip: drop unnecessary include
ARM: vexpress: drop unnecessary include
ARM: brcmstb: drop unnecessary include
arch/arm/include/asm/cacheflush.h | 1 +
arch/arm/mach-bcm/platsmp-brcmstb.c | 1 -
arch/arm/mach-mvebu/pmsu.c | 1 -
arch/arm/mach-rockchip/platsmp.c | 1 -
arch/arm/mach-vexpress/dcscb.c | 1 -
arch/arm/mach-vexpress/tc2_pm.c | 1 -
6 files changed, 1 insertion(+), 5 deletions(-)
--
1.9.1
next reply other threads:[~2014-09-30 1:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 1:35 Brian Norris [this message]
2014-09-30 1:35 ` [PATCH 1/5] ARM: include missing cp15.h header Brian Norris
2014-09-30 1:35 ` [PATCH 2/5] ARM: mvebu: drop unnecessary include Brian Norris
2014-09-30 1:35 ` [PATCH 3/5] ARM: rockchip: " Brian Norris
2014-09-30 1:35 ` [PATCH 4/5] ARM: vexpress: " Brian Norris
2014-09-30 1:35 ` [PATCH 5/5] ARM: brcmstb: " Brian Norris
2014-09-30 4:30 ` [PATCH 0/5] ARM: move #include <asm/cp15.h> into cacheflush.h Nicolas Pitre
2014-09-30 10:03 ` Russell King - ARM Linux
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=1412040930-16864-1-git-send-email-computersforpeace@gmail.com \
--to=computersforpeace@gmail.com \
--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).