From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/5] am33xx data for v3.6 merge window
Date: Tue, 10 Jul 2012 06:05:56 -0700 [thread overview]
Message-ID: <E1SoaA9-0001Je-6V@merlin.infradead.org> (raw)
In-Reply-To: <pull-1341925556-888624>
The following changes since commit ecc46cfdad7499a21296f0757059c4965f1fbc98:
ARM: OMAP2+: Remove unnecessary ifdef around __omap2_set_globals (2012-07-05 08:05:15 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-devel-am33xx-data-for-v3.6
for you to fetch changes up to 79ab2664336d73245023a236345bb31f2b0a2dfe:
Merge tag 'omap-devel-e-for-3.5' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into devel-am33xx-data (2012-07-05 08:18:04 -0700)
----------------------------------------------------------------
This branch adds clock data for am33xx. Note that eventually these
will use the common clock framework, but those patches are not quite
ready yet for omaps. This branch depends on omap-cleanup-part2-for-v3.6
branch.
----------------------------------------------------------------
Paul Walmsley (1):
ARM: OMAP3+: clock: Move common clksel_rate & clock data to common file
Tony Lindgren (1):
Merge tag 'omap-devel-e-for-3.5' of git://git.kernel.org/.../pjw/omap-pending into devel-am33xx-data
Vaibhav Hiremath (1):
ARM: OMAP3+: clock33xx: Add AM33XX clock tree data
arch/arm/mach-omap2/Makefile | 1 +
arch/arm/mach-omap2/clock.h | 14 +
arch/arm/mach-omap2/clock33xx_data.c | 1105 +++++++++++++++++++++++++
arch/arm/mach-omap2/clock3xxx_data.c | 20 +-
arch/arm/mach-omap2/clock44xx_data.c | 72 --
arch/arm/mach-omap2/clock_common_data.c | 77 ++
arch/arm/mach-omap2/io.c | 2 +
arch/arm/plat-omap/include/plat/clkdev_omap.h | 1 +
8 files changed, 1204 insertions(+), 88 deletions(-)
create mode 100644 arch/arm/mach-omap2/clock33xx_data.c
next prev parent reply other threads:[~2012-07-10 13:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 13:05 [GIT PULL 1/5] omap device tree changes for v3.6 merge window Tony Lindgren
2012-07-10 13:05 ` [GIT PULL 2/5] omap board " Tony Lindgren
2012-07-10 13:05 ` Tony Lindgren
2012-07-10 13:05 ` [GIT PULL 3/5] omap cleanup part2 " Tony Lindgren
2012-07-10 13:05 ` [GIT PULL 5/5] minimal omap5 support " Tony Lindgren
2012-07-10 13:05 ` Tony Lindgren
2012-07-10 13:05 ` [GIT PULL 3/5] omap cleanup part2 " Tony Lindgren
2012-07-10 13:05 ` Tony Lindgren [this message]
2012-07-10 13:05 ` [GIT PULL 4/5] am33xx data " Tony Lindgren
[not found] ` <E1SoaE5-0001gM-89@merlin.infradead.org>
2012-07-10 13:42 ` [GIT PULL 5/5] minimal omap5 support " Tony Lindgren
2012-07-10 13:42 ` Tony Lindgren
2012-07-10 15:53 ` Arnd Bergmann
2012-07-10 15:53 ` Arnd Bergmann
2012-07-11 6:04 ` Tony Lindgren
2012-07-11 6:04 ` Tony Lindgren
2012-07-13 6:14 ` [GIT PULL 1/5] omap device tree changes " Mohammed, Afzal
2012-07-13 6:14 ` Mohammed, Afzal
2012-07-13 6:41 ` Tony Lindgren
2012-07-13 6:41 ` Tony Lindgren
2012-07-13 7:56 ` Tony Lindgren
2012-07-13 7:56 ` Tony Lindgren
2012-08-07 7:13 ` Tony Lindgren
2012-08-07 7:13 ` Tony Lindgren
2012-08-07 7:29 ` Mohammed, Afzal
2012-08-07 7:29 ` Mohammed, Afzal
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=E1SoaA9-0001Je-6V@merlin.infradead.org \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.