linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/7] Switch ARM platforms from integrator-flash to physmap
Date: Thu, 17 Mar 2011 13:03:41 +0000	[thread overview]
Message-ID: <1300367028-3916-1-git-send-email-marc.zyngier@arm.com> (raw)

As the integrator-flash driver is mostly a duplicate of physmap,
move all users of this driver to physmap and get rid of the
then unused driver.

This patch set has been ok'ed by RMK, but the merge path seems
unclear. David Woodhouse cc-ed on the whole patch set in case he'd
prefer to merge it via his MTD tree.

Changes since v3:
- Dropped patch for aaec2000 platform (removed from tree)
- Rebased against next-20110317

Changes since v2:
- Add integrator-flash's init()/exit() methods in order to control
  write access to the various onboard programmable components, as
  per RMK request.
- Rebased against 2.6.38-rc2

Changes since initial revision:
- Rebased against linux-next (20110107). It should apply cleanly
  on top of Linus' tree, except for a small conflict in the last
  patch of the serie.

Marc Zyngier (7):
  MTD: Add integrator-flash feature to physmap
  ARM: Realview: Use physmap driver instead of integrator-flash
  ARM: Versatile: Use physmap driver instead of integrator-flash
  ARM: VExpress: Use physmap driver instead of integrator-flash
  ARM: Integrator/AP: Use physmap driver instead of integrator-flash
  ARM: Integrator/CP: Use physmap driver instead of integrator-flash
  MTD: Remove integrator-flash

 arch/arm/configs/realview-smp_defconfig  |    2 +-
 arch/arm/configs/realview_defconfig      |    2 +-
 arch/arm/configs/versatile_defconfig     |    2 +-
 arch/arm/mach-integrator/integrator_ap.c |   13 +-
 arch/arm/mach-integrator/integrator_cp.c |   13 +-
 arch/arm/mach-realview/core.c            |   31 +---
 arch/arm/mach-versatile/core.c           |   31 +---
 arch/arm/mach-vexpress/v2m.c             |   22 +--
 drivers/mtd/Kconfig                      |    3 +-
 drivers/mtd/maps/Makefile                |    1 -
 drivers/mtd/maps/integrator-flash.c      |  309 ------------------------------
 drivers/mtd/maps/physmap.c               |   16 ++-
 include/linux/mtd/physmap.h              |    2 +
 13 files changed, 45 insertions(+), 402 deletions(-)
 delete mode 100644 drivers/mtd/maps/integrator-flash.c

             reply	other threads:[~2011-03-17 13:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 13:03 Marc Zyngier [this message]
2011-03-17 13:03 ` [PATCH v4 1/7] MTD: Add integrator-flash feature to physmap Marc Zyngier
2011-05-15  7:41   ` Russell King - ARM Linux
2011-05-16 12:52     ` Marc Zyngier
2011-05-16 13:00       ` Russell King - ARM Linux
2011-05-16 13:11         ` Marc Zyngier
2011-03-17 13:03 ` [PATCH v4 2/7] ARM: Realview: Use physmap driver instead of integrator-flash Marc Zyngier
2011-03-17 13:03 ` [PATCH v4 3/7] ARM: Versatile: " Marc Zyngier
2011-03-17 13:03 ` [PATCH v4 4/7] ARM: VExpress: " Marc Zyngier
2011-03-17 13:03 ` [PATCH v4 5/7] ARM: Integrator/AP: " Marc Zyngier
2011-03-17 13:03 ` [PATCH v4 6/7] ARM: Integrator/CP: " Marc Zyngier
2011-03-17 13:03 ` [PATCH v4 7/7] MTD: Remove integrator-flash Marc Zyngier

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=1300367028-3916-1-git-send-email-marc.zyngier@arm.com \
    --to=marc.zyngier@arm.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).