From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: omap-clock-fixes branch available
Date: Fri, 10 Apr 2009 12:22:00 -0700 [thread overview]
Message-ID: <20090410192200.GB8345@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0904092111240.15126@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [090409 20:12]:
>
> Hello Tony et al.,
>
> Please pull this omap-clock-fixes branch. Once rmk gets back from his
> holiday, these will be posted to linux-arm-kernel.
Thanks, I've pulled it into l-o master.
Tony
>
>
> - Paul
>
>
> The following changes since commit 15f7176eb1cccec0a332541285ee752b935c1c85:
> Linus Torvalds (1):
> Merge git://git.kernel.org/.../davem/net-2.6
>
> are available in the git repository at:
>
> git://git.pwsan.com/linux-2.6 omap-clock-fixes
>
> Kevin Hilman (1):
> OMAP: dmtimer: enable all timers to be wakeup events
>
> Paul Walmsley (4):
> OMAP2xxx clock: init osc_ck, sys_ck internal lists early
> OMAP2xxx clock: fix broken cpu_mask code
> OMAP3 GPTIMER: fix GPTIMER12 IRQ
> OMAP2/3 GPTIMER: allow system tick GPTIMER to be changed in board-*.c files
>
> Sergio Aguirre (1):
> OMAP3: clock: Camera module doesn't have IDLEST bit
>
> arch/arm/mach-omap2/board-omap3beagle.c | 4 ++
> arch/arm/mach-omap2/clock24xx.c | 15 +++-----
> arch/arm/mach-omap2/clock24xx.h | 10 +++++-
> arch/arm/mach-omap2/clock34xx.h | 7 ++--
> arch/arm/mach-omap2/timer-gp.c | 48 ++++++++++++++++++++++++++--
> arch/arm/plat-omap/dmtimer.c | 28 ++++++++++------
> arch/arm/plat-omap/include/mach/dmtimer.h | 2 +-
> arch/arm/plat-omap/include/mach/timer-gp.h | 17 ++++++++++
> 8 files changed, 102 insertions(+), 29 deletions(-)
> create mode 100644 arch/arm/plat-omap/include/mach/timer-gp.h
prev parent reply other threads:[~2009-04-10 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 3:12 omap-clock-fixes branch available Paul Walmsley
2009-04-10 19:22 ` Tony Lindgren [this message]
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=20090410192200.GB8345@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
/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