From: Magnus Damm <magnus.damm@gmail.com>
To: linux-sh@vger.kernel.org
Subject: [PATCH 00/06] ARM: shmobile: Kconfig and Makefile cleanups
Date: Wed, 20 Aug 2014 13:31:21 +0000 [thread overview]
Message-ID: <20140820133121.808.91022.sendpatchset@w520> (raw)
ARM: shmobile: Kconfig and Makefile cleanups
[PATCH 01/06] ARM: shmobile: Consolidate GPIOLIB Kconfig bits
[PATCH 02/06] ARM: shmobile: Introduce a Kconfig entry for R-Mobile
[PATCH 03/06] ARM: shmobile: Introduce a Kconfig entry for R-Car Gen1
[PATCH 04/06] ARM: shmobile: Introduce a Kconfig entry for R-Car Gen2
[PATCH 05/06] ARM: shmobile: Cleanup pm-rcar.o build using Kconfig
[PATCH 06/06] ARM: shmobile: Cleanup pm-rmobile.o build using Kconfig
Update the ARM mach-shmobile Kconfig and Makefile to prepare for
multiplatform support of R-Mobile SoCs. While at it do various
cleanups - thanks to Simon Horman for suggesting using Kconfig
for pm-rmobile.o. I applied the same idea to patch 5. Thanks to
Geert Uytterhoeven for pointing out the mess in the Kconfig files,
hopefully this cleanup series is a step in the right direction.
Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---
Written on top of renesas-devel-20140820-v3.17-rc1
Only lightly build tested.
arch/arm/mach-shmobile/Kconfig | 66 +++++++++++++++++++----------------
arch/arm/mach-shmobile/Makefile | 36 ++++++++-----------
arch/arm/mach-shmobile/pm-rcar.c | 4 --
arch/arm/mach-shmobile/pm-rmobile.c | 2 -
arch/arm/mach-shmobile/pm-rmobile.h | 4 +-
5 files changed, 54 insertions(+), 58 deletions(-)
next reply other threads:[~2014-08-20 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 13:31 Magnus Damm [this message]
2014-08-20 14:26 ` [PATCH 00/06] ARM: shmobile: Kconfig and Makefile cleanups Geert Uytterhoeven
2014-08-22 3:05 ` Simon Horman
2014-08-25 4:04 ` Magnus Damm
2014-08-27 4:19 ` Simon Horman
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=20140820133121.808.91022.sendpatchset@w520 \
--to=magnus.damm@gmail.com \
--cc=linux-sh@vger.kernel.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).