From: Shawn Guo <shawn.guo@linaro.org>
To: linux-kernel@vger.kernel.org
Cc: grant.likely@secretlab.ca, arnd@arndb.de, kernel@pengutronix.de,
linux-arm-kernel@lists.infradead.org, patches@linaro.org
Subject: [PATCH v3 0/3] Move Freescale MXS gpio driver into drivers/gpio
Date: Sat, 4 Jun 2011 18:55:37 +0800 [thread overview]
Message-ID: <1307184940-16291-1-git-send-email-shawn.guo@linaro.org> (raw)
The patch set moves Freescale MXS gpio driver from mach-mxs into
drivers/gpio.
Changes since v2:
* Add a patch as the first one just copying mach-mxs gpio into
drivers/gpio
* Add the missing ".owner = THIS_MOUDLE" for gpio-mxs driver
Shawn Guo (3):
gpio: gpio-mxs: copy mach-mxs/gpio.c into drivers/gpio
gpio: gpio-mxs: make it work for Freescale MXS architecture
ARM: mxs: use gpio-mxs driver by adding platform device
arch/arm/mach-mxs/Makefile | 2 +-
arch/arm/mach-mxs/devices.c | 11 +
arch/arm/mach-mxs/devices/Makefile | 1 +
arch/arm/mach-mxs/devices/platform-gpio-mxs.c | 53 +++++
arch/arm/mach-mxs/gpio.h | 34 ---
arch/arm/mach-mxs/include/mach/devices-common.h | 2 +
arch/arm/mach-mxs/mach-mx28evk.c | 1 -
arch/arm/mach-mxs/mm-mx23.c | 1 -
arch/arm/mach-mxs/mm-mx28.c | 1 -
drivers/gpio/Makefile | 1 +
.../arm/mach-mxs/gpio.c => drivers/gpio/gpio-mxs.c | 227 ++++++++++++--------
11 files changed, 202 insertions(+), 132 deletions(-)
next reply other threads:[~2011-06-04 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 10:55 Shawn Guo [this message]
2011-06-04 10:55 ` [PATCH v3 1/3] gpio: gpio-mxs: copy mach-mxs/gpio.c into drivers/gpio Shawn Guo
2011-06-04 22:29 ` Grant Likely
2011-06-05 16:23 ` Shawn Guo
2011-06-06 8:10 ` Grant Likely
2011-06-04 10:55 ` [PATCH v3 2/3] gpio: gpio-mxs: make it work for Freescale MXS architecture Shawn Guo
2011-06-04 10:55 ` [PATCH v3 3/3] ARM: mxs: use gpio-mxs driver by adding platform device Shawn Guo
2011-06-04 22:34 ` Grant Likely
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=1307184940-16291-1-git-send-email-shawn.guo@linaro.org \
--to=shawn.guo@linaro.org \
--cc=arnd@arndb.de \
--cc=grant.likely@secretlab.ca \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.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).