linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/7] omap gpmc cleanup for v3.7 merge window
Date: Thu, 13 Sep 2012 19:34:10 -0700	[thread overview]
Message-ID: <mailman.9.1347590089.1458.linux-arm-kernel@lists.infradead.org> (raw)
In-Reply-To: <pull-1347590052-683636>

The following changes since commit fea7a08acb13524b47711625eebea40a0ede69a0:

  Linux 3.6-rc3 (2012-08-22 13:29:06 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-devel-gpmc-fixed-for-v3.7

for you to fetch changes up to 5c4684557b7e37afd42fa35f420f2f28bfb75442:

  mtd: nand: omap2: use gpmc provided irqs (2012-08-30 12:53:24 -0700)

----------------------------------------------------------------
Changes for GPMC (General Purpose Memory Controller) that take it
closer for being just a regular device driver.

----------------------------------------------------------------
Afzal Mohammed (10):
      ARM: OMAP2+: gpmc: update nand register helper
      ARM: OMAP2+: gpmc-nand: update gpmc-nand regs
      mtd: nand: omap2: handle nand on gpmc
      ARM: OMAP2+: gpmc-nand: update resource with memory
      ARM: OMAP2+: gpmc-onenand: provide memory as resource
      mtd: nand: omap2: obtain memory from resource
      mtd: onenand: omap2: obtain memory from resource
      ARM: OMAP2+: gpmc: Modify interrupt handling
      ARM: OMAP2+: gpmc-nand: Modify Interrupt handling
      mtd: nand: omap2: use gpmc provided irqs

 arch/arm/mach-omap2/gpmc-nand.c        |   28 ++-
 arch/arm/mach-omap2/gpmc-onenand.c     |   23 ++-
 arch/arm/mach-omap2/gpmc.c             |  156 +++++++++++++++--
 arch/arm/plat-omap/include/plat/gpmc.h |   19 ++
 arch/arm/plat-omap/include/plat/nand.h |    2 +-
 drivers/mtd/nand/omap2.c               |  301 ++++++++++++++++++++++++--------
 drivers/mtd/onenand/omap2.c            |   29 +--
 7 files changed, 445 insertions(+), 113 deletions(-)

  reply	other threads:[~2012-09-14  2:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14  2:34 [GIT PULL 1/7] omap non-critical fixes for v3.7 merge window Tony Lindgren
2012-09-14  2:34 ` Tony Lindgren [this message]
2012-09-14  2:34 ` [GIT PULL 2/7] omap device changes " Tony Lindgren
2012-09-14  2:34 ` [GIT PULL 4/7] omap custom atag removal " Tony Lindgren
2012-09-14  2:34 ` [GIT PULL 5/7] omap sparse irq and local hardware.h cleanup " Tony Lindgren
2012-09-14  2:34 ` [GIT PULL 6/7] omap makefile and sparse " Tony Lindgren
2012-09-14  2:34 ` [GIT PULL 7/7] am33xx hwmod data " Tony Lindgren
     [not found] ` <E1TCLkq-0006f8-Qp@merlin.infradead.org>
2012-09-14 17:55   ` [GIT PULL 5/7] omap sparse irq and local hardware.h cleanup " Tony Lindgren
     [not found] ` <E1TCLkx-0006iv-9h@merlin.infradead.org>
2012-09-17  3:08   ` [GIT PULL 6/7] omap makefile and sparse " Olof Johansson
  -- strict thread matches above, loose matches on Subject: below --
2012-09-14  2:18 [GIT PULL 1/7] omap non-critical fixes " Tony Lindgren
2012-09-14  2:18 ` [GIT PULL 3/7] omap gpmc cleanup " Tony Lindgren
     [not found] ` <5052940d.06d3e00a.5f71.ffffd0d4SMTPIN_ADDED@mx.google.com>
2012-09-17  2:52   ` Olof Johansson

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=mailman.9.1347590089.1458.linux-arm-kernel@lists.infradead.org \
    --to=tony@atomide.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).