From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Pending S3C64xx updates
Date: Tue, 24 Jan 2012 21:31:27 +0000 [thread overview]
Message-ID: <20120124213127.GH1135@opensource.wolfsonmicro.com> (raw)
This patch series is a collection of s3c64xx updates I've had hanging
round in my tree for varying lengths of time that it'd be good to get
merged. There's no particularly relationship between them except that
they're all for s3c64xx.
Mark Brown (4):
ARM: S3C64XX: Make s3c64xx_init_uarts() static
ARM: S3C64XX: Define some additional always off clocks
ARM: S3C6410: Use device names for both I2C clocks
ARM: S3C64XX: Add hookup for Tomatin module on Cragganmore
arch/arm/mach-s3c64xx/clock.c | 106 ++++++++++++++++++++++++++
arch/arm/mach-s3c64xx/common.c | 2 +-
arch/arm/mach-s3c64xx/mach-crag6410-module.c | 27 ++++++-
arch/arm/mach-s3c64xx/mach-crag6410.c | 11 +++-
4 files changed, 143 insertions(+), 3 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/20120124/09286098/attachment.sig>
next reply other threads:[~2012-01-24 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 21:31 Mark Brown [this message]
2012-01-24 21:31 ` [PATCH 1/4] ARM: S3C64XX: Make s3c64xx_init_uarts() static Mark Brown
2012-01-24 21:31 ` [PATCH 2/4] ARM: S3C64XX: Define some additional always off clocks Mark Brown
2012-01-24 21:31 ` [PATCH 3/4] ARM: S3C6410: Use device names for both I2C clocks Mark Brown
2012-01-24 21:31 ` [PATCH 4/4] ARM: S3C64XX: Add hookup for Tomatin module on Cragganmore Mark Brown
2012-01-27 1:33 ` [PATCH 0/4] Pending S3C64xx updates Kukjin Kim
2012-01-27 11:27 ` Mark Brown
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=20120124213127.GH1135@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).