From: Paul Mundt <lethal@linux-sh.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] rmobile updates for 2.6.37-rc2
Date: Mon, 08 Nov 2010 01:13:27 +0000 [thread overview]
Message-ID: <20101108011327.GA10728@linux-sh.org> (raw)
As discussed at kernel summit, here's the first attempt at bringing the
SH/R-Mobile bits in to a more coherent branch topology within the SH tree
proper. Following this I'll be killing off my ARM tree completely and
simply sticking with this approach.
There's nothing really exciting here, with the exception of the FSIDIV
clock addition. This is something that the HDMI audio depends on and has
up until now been blocked on core infrastructure patches in the SH tree,
all of which were merged during -rc1. These have all been sitting in
-next for the last few weeks and have had extensive out-of-tree testing
since well before that, so there should be no real surprises here.
Please pull from:
master.kernel.org:/pub/scm/linux/kernel/git/lethal/sh-2.6.git rmobile-fixes-for-linus
Which contains:
Guennadi Liakhovetski (1):
ARM: mach-shmobile: fix sh7372 after a recent clock framework rework
Kuninori Morimoto (2):
ARM: mach-shmobile: clock-sh7372: Add FSIDIV clock support
ARM: mach-shmobile: ap4evb: Add HDMI sound support
Magnus Damm (1):
ARM: shmobile: remove sh_timer_config clk member
Paul Mundt (3):
ARM: mach-shmobile: include drivers/sh/Kconfig
ARM: mach-shmobile: Allow GPIO chips to register IRQ mappings.
mmc: sh_mmcif: Convert extern inline to static inline.
arch/arm/mach-shmobile/Kconfig | 2 +
arch/arm/mach-shmobile/board-ap4evb.c | 46 +++++++++++-
arch/arm/mach-shmobile/clock-sh7372.c | 102 ++++++++++++++++++++++++++
arch/arm/mach-shmobile/include/mach/gpio.h | 4 +-
arch/arm/mach-shmobile/include/mach/sh7372.h | 2 +
drivers/clocksource/sh_cmt.c | 10 +--
drivers/clocksource/sh_mtu2.c | 10 +--
drivers/clocksource/sh_tmu.c | 10 +--
include/linux/mmc/sh_mmcif.h | 18 ++--
include/linux/sh_timer.h | 1 -
10 files changed, 171 insertions(+), 34 deletions(-)
next reply other threads:[~2010-11-08 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 1:13 Paul Mundt [this message]
2010-11-24 13:50 ` [GIT PULL] rmobile updates for 2.6.37-rc4 Paul Mundt
2010-11-24 22:02 ` Linus Torvalds
2010-11-25 6:57 ` Paul Mundt
2010-12-20 16:14 ` [GIT PULL] rmobile updates for 2.6.37-rc7 Paul Mundt
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=20101108011327.GA10728@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=torvalds@linux-foundation.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).