linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] Cragganmore updates
Date: Wed, 17 Oct 2012 16:38:15 +0900	[thread overview]
Message-ID: <20121017073813.GI14199@opensource.wolfsonmicro.com> (raw)

The following changes since commit ddffeb8c4d0331609ef2581d84de4d763607bd37:

  Linux 3.7-rc1 (2012-10-14 14:41:04 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git tags/crag6410

for you to fetch changes up to c8a825563eae03e657b191c2b4948f7613ae91b6:

  ARM: S3C64XX: Add handset module to probed Glenfarclas modules (2012-10-16 14:09:01 +0900)

----------------------------------------------------------------
ARM: S3C64XX: Cragganmore updates

There's a bunch of things in here (some have been posted before I
believe), the main thing is the update to support muliple board
revisions but there's also some new modules added.

----------------------------------------------------------------
Mark Brown (8):
      ARM: S3C64XX: Add more Glenfarclas module ID strings
      ARM: S3C64XX: Update hookup for Arizona class devices
      ARM: S3C64XX: Provide platform data for Tomatin/Balblair on Cragganmore
      ARM: S3C64XX: Handle revision-specific differences in Cragganmore modules
      ARM: S3C64XX: Handle new Amrut modules on Cragganmore
      ARM: S3C64XX: Add hookup for Deanston module on Cragganmore
      ARM: S3C64XX: Add WM2200 module for Cragganmore
      ARM: S3C64XX: Add handset module to probed Glenfarclas modules

 arch/arm/mach-s3c64xx/mach-crag6410-module.c |  141 +++++++++++++++++++++-----
 arch/arm/mach-s3c64xx/mach-crag6410.c        |   29 +++++-
 2 files changed, 144 insertions(+), 26 deletions(-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121017/62e1e0ed/attachment.sig>

             reply	other threads:[~2012-10-17  7:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17  7:38 Mark Brown [this message]
2012-10-17  7:38 ` [PATCH 1/8] ARM: S3C64XX: Add more Glenfarclas module ID strings Mark Brown
2012-10-17  7:38   ` [PATCH] mfd: wm5102: Mark some more status registers as volatile Mark Brown
2012-10-17  7:38   ` [PATCH 2/8] ARM: S3C64XX: Update hookup for Arizona class devices Mark Brown
2012-10-17  7:38   ` [PATCH 3/8] ARM: S3C64XX: Provide platform data for Tomatin/Balblair on Cragganmore Mark Brown
2012-10-17  7:38   ` [PATCH 4/8] ARM: S3C64XX: Handle revision-specific differences in Cragganmore modules Mark Brown
2012-10-17  7:38   ` [PATCH 5/8] ARM: S3C64XX: Handle new Amrut modules on Cragganmore Mark Brown
2012-10-17  7:38   ` [PATCH 6/8] ARM: S3C64XX: Add hookup for Deanston module " Mark Brown
2012-10-17  7:38   ` [PATCH 7/8] ARM: S3C64XX: Add WM2200 module for Cragganmore Mark Brown
2012-10-17  7:38   ` [PATCH 8/8] ARM: S3C64XX: Add handset module to probed Glenfarclas modules Mark Brown
2012-10-17  9:48 ` [PATCH 0/8] Cragganmore updates Kukjin Kim

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=20121017073813.GI14199@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.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).