From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] Fix indirect inclusion to <mach/hardware.h>
Date: Mon, 17 Oct 2011 14:15:05 +0800 [thread overview]
Message-ID: <1318832110-29289-1-git-send-email-shawn.guo@linaro.org> (raw)
With rmk's mach/gpio.h cleanup series merged into arm-soc/imx tree,
plat-mxc/include/mach/gpio.h will become an empty file waiting for
a global removal of mach/gpio.h.
Currently, this mach/gpio.h includes mach/hardware.h. Once mach/gpio.h
becomes an empty file, we will hit a number of imx build errors caused
by the indirect inclusion to mach/hardware.h. This series is trying to
address these errors before above two trees gets merged, which will
happen pretty soon, I believe.
Shawn Guo (5):
arm/imx: remove mx31_setup_weimcs() from mx31.h
arm/imx: explicitly includes mach/hardware.h in mach-kzm_arm11_01.c
arm/imx: remove mx27_setup_weimcs() from mx27.h
arm/imx: explicitly includes mach/hardware.h in pm-imx27.c
mmc: mxcmmc: explicitly includes mach/hardware.h
arch/arm/mach-imx/mach-kzm_arm11_01.c | 1 +
arch/arm/mach-imx/mach-pcm038.c | 4 +++-
arch/arm/mach-imx/mach-qong.c | 5 ++++-
arch/arm/mach-imx/pm-imx27.c | 2 +-
arch/arm/plat-mxc/include/mach/mx27.h | 14 --------------
arch/arm/plat-mxc/include/mach/mx31.h | 14 --------------
drivers/mmc/host/mxcmmc.c | 1 +
7 files changed, 10 insertions(+), 31 deletions(-)
next reply other threads:[~2011-10-17 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 6:15 Shawn Guo [this message]
2011-10-17 6:15 ` [PATCH 1/5] arm/imx: remove mx31_setup_weimcs() from mx31.h Shawn Guo
2011-10-17 6:15 ` [PATCH 2/5] arm/imx: explicitly includes mach/hardware.h in mach-kzm_arm11_01.c Shawn Guo
2011-10-17 6:15 ` [PATCH 3/5] arm/imx: remove mx27_setup_weimcs() from mx27.h Shawn Guo
2011-10-17 6:15 ` [PATCH 4/5] arm/imx: explicitly includes mach/hardware.h in pm-imx27.c Shawn Guo
2011-10-17 6:15 ` [PATCH 5/5] mmc: mxcmmc: explicitly includes mach/hardware.h Shawn Guo
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=1318832110-29289-1-git-send-email-shawn.guo@linaro.org \
--to=shawn.guo@linaro.org \
--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).