From: bryan.wu@canonical.com (Bryan Wu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] footbridge consolidation patches
Date: Mon, 13 Jun 2011 14:39:39 +0800 [thread overview]
Message-ID: <1307947185-5159-1-git-send-email-bryan.wu@canonical.com> (raw)
When trying to convert old leds event driver to led trigger drivers, I reviewed
the code of mach-footbridge. move seperated PCI code and leds code into a
single board files like other machines.
leds trigger code is based on Linus Walleij's driver in
arch/arm/plat-versatile/leds.c
Built successfully with footbridge_defconfig.
Bryan Wu (6):
arm: footbridge: consolidation code of CATS machine
arm: footbridge: consolidation code of EBSA285 machine
arm: footbridge: consolidation code of Netwinder machine
arm: footbridge: consolidation code of Compaq Personal Server
arm: footbridge: convert old leds event driver to led gpio trigger
driver of Netwinder
arm: footbridge: convert old leds event driver to led trigger drivers
of EBSA285
arch/arm/mach-footbridge/Kconfig | 6 +
arch/arm/mach-footbridge/Makefile | 15 +-
arch/arm/mach-footbridge/cats-hw.c | 95 ----
arch/arm/mach-footbridge/cats-pci.c | 58 ---
arch/arm/mach-footbridge/cats.c | 143 ++++++
arch/arm/mach-footbridge/ebsa285-leds.c | 139 ------
arch/arm/mach-footbridge/ebsa285-pci.c | 48 --
arch/arm/mach-footbridge/ebsa285.c | 114 +++++-
arch/arm/mach-footbridge/netwinder-hw.c | 660 --------------------------
arch/arm/mach-footbridge/netwinder-leds.c | 139 ------
arch/arm/mach-footbridge/netwinder-pci.c | 62 ---
arch/arm/mach-footbridge/netwinder.c | 737 +++++++++++++++++++++++++++++
arch/arm/mach-footbridge/personal-pci.c | 56 ---
arch/arm/mach-footbridge/personal.c | 46 ++
14 files changed, 1047 insertions(+), 1271 deletions(-)
delete mode 100644 arch/arm/mach-footbridge/cats-hw.c
delete mode 100644 arch/arm/mach-footbridge/cats-pci.c
create mode 100644 arch/arm/mach-footbridge/cats.c
delete mode 100644 arch/arm/mach-footbridge/ebsa285-leds.c
delete mode 100644 arch/arm/mach-footbridge/ebsa285-pci.c
delete mode 100644 arch/arm/mach-footbridge/netwinder-hw.c
delete mode 100644 arch/arm/mach-footbridge/netwinder-leds.c
delete mode 100644 arch/arm/mach-footbridge/netwinder-pci.c
create mode 100644 arch/arm/mach-footbridge/netwinder.c
delete mode 100644 arch/arm/mach-footbridge/personal-pci.c
--
1.7.5
next reply other threads:[~2011-06-13 6:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 6:39 Bryan Wu [this message]
2011-06-13 6:39 ` [PATCH 1/6] arm: footbridge: consolidation code of CATS machine Bryan Wu
2011-06-13 6:39 ` [PATCH 2/6] arm: footbridge: consolidation code of EBSA285 machine Bryan Wu
2011-06-13 6:39 ` [PATCH 3/6] arm: footbridge: consolidation code of Netwinder machine Bryan Wu
2011-06-13 6:39 ` [PATCH 4/6] arm: footbridge: consolidation code of Compaq Personal Server Bryan Wu
2011-06-13 6:39 ` [PATCH 5/6] arm: footbridge: convert old leds event driver to led gpio trigger driver of Netwinder Bryan Wu
2011-06-13 8:23 ` Russell King - ARM Linux
2011-06-13 10:02 ` Bryan Wu
2011-06-13 6:39 ` [PATCH 6/6] arm: footbridge: convert old leds event driver to led trigger drivers of EBSA285 Bryan Wu
2011-06-13 8:20 ` [PATCH 0/6] footbridge consolidation patches Russell King - ARM Linux
2011-06-13 9:57 ` Bryan Wu
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=1307947185-5159-1-git-send-email-bryan.wu@canonical.com \
--to=bryan.wu@canonical.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).