From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP2+: System timer updates
Date: Wed, 3 Apr 2013 11:04:47 -0700 [thread overview]
Message-ID: <20130403180447.GX10155@atomide.com> (raw)
In-Reply-To: <515A3E01.1060308@ti.com>
* Jon Hunter <jon-hunter@ti.com> [130401 19:14]:
> The following changes since commit 2d61aecee8f32259920cdf90a452fa26ffc64e9f:
>
> Merge commit '6bb27d7349db51b50c40534710fe164ca0d58902' into omap-timer-for-v3.10 (2013-04-01 13:47:29 -0500)
>
> are available in the git repository at:
>
>
> git://github.com/jonhunter/linux.git omap-timer-for-v3.10
>
> for you to fetch changes up to 4615943cf3a531bc76f589c22bd366da092b7c0f:
>
> ARM: OMAP4+: Fix sparse warning in system timers (2013-04-01 13:49:46 -0500)
>
> ----------------------------------------------------------------
> This series consists mainly of clean-ups for clockevents and
> clocksource timers on OMAP2+ devices. The most significant change
> in functionality comes from the 5th patch which is changing the
> selection of the clocksource timer for OMAP3 and AM335x devices
> when gptimers are used for clocksource.
>
> This series is dependent on commit 7185684 (ARM: OMAP: use
> consistent error checking) from RMK's clean-up branch and commit
> 6bb27d7 (ARM: delete struct sys_timer)
Thanks pulling into omap-for-v3.10/timer. I ended up merging this
with omap-for-v3.10/fixes-non-critical because of the omap5 merge
conflict.
Regards,
Tony
> ----------------------------------------------------------------
>
> Jon Hunter (7):
> ARM: OMAP2+: Display correct system timer name
> ARM: OMAP2+: Remove hard-coded test on timer ID
> ARM: OMAP2+: Simplify system timer clock definitions
> ARM: OMAP2+: Simplify system timers definitions
> ARM: OMAP3: Update clocksource timer selection
> ARM: OMAP2+: Store ID of system timers in timer structure
> ARM: OMAP4+: Fix sparse warning in system timers
>
> arch/arm/mach-omap2/board-cm-t3517.c | 2 +-
> arch/arm/mach-omap2/board-generic.c | 2 +-
> arch/arm/mach-omap2/common.h | 3 +-
> arch/arm/mach-omap2/timer.c | 121 +++++++++++++++++-----------------
> 4 files changed, 65 insertions(+), 63 deletions(-)
prev parent reply other threads:[~2013-04-03 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 2:10 [GIT PULL] ARM: OMAP2+: System timer updates Jon Hunter
2013-04-03 18:04 ` 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=20130403180447.GX10155@atomide.com \
--to=tony@atomide.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).