From: mingo@kernel.org (Ingo Molnar)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] clockevents/clocksources: 3.13 fixes
Date: Wed, 15 Jan 2014 07:41:32 +0100 [thread overview]
Message-ID: <20140115064132.GA12484@gmail.com> (raw)
In-Reply-To: <52C14E45.5040403@linaro.org>
* Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>
> Hi Thomas and Ingo,
>
> here is a pull request for a single fix for 3.13. It is based on the
> latest timers/urgent update.
>
> * Soren Brinkmann fixed the cadence_ttc driver where a call to
> clk_get_rate happens in an interrupt context. More precisely in an
> IPI when the broadcast timer is initialized for each cpu in the
> cpuidle driver
>
> Thanks
> -- Daniel
>
> The following changes since commit b0031f227e47919797dc0e1c1990f3ef151ff0cc:
>
> Merge tag 's2mps11-build' of
> git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator
> (2013-12-17 12:57:36 -0800)
>
> are available in the git repository at:
>
>
> git://git.linaro.org/people/daniel.lezcano/linux.git
> clockevents/3.13-fixes
>
> for you to fetch changes up to c1dcc927dae01dfd4904ee82ce2c00b50eab6dc3:
>
> clocksource: cadence_ttc: Fix mutex taken inside interrupt context
> (2013-12-30 11:32:24 +0100)
>
> ----------------------------------------------------------------
> Soren Brinkmann (1):
> clocksource: cadence_ttc: Fix mutex taken inside interrupt context
>
> drivers/clocksource/cadence_ttc_timer.c | 21 +++++++++++++--------
> 1 file changed, 13 insertions(+), 8 deletions(-)
Pulled into tip:timers/urgent, thanks Daniel!
Ingo
prev parent reply other threads:[~2014-01-15 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 10:43 [GIT PULL] clockevents/clocksources: 3.13 fixes Daniel Lezcano
2013-12-30 10:44 ` [PATCH] clocksource: cadence_ttc: Fix mutex taken inside interrupt context Daniel Lezcano
2014-01-14 15:01 ` [GIT PULL] clockevents/clocksources: 3.13 fixes Daniel Lezcano
2014-01-15 6:41 ` Ingo Molnar [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=20140115064132.GA12484@gmail.com \
--to=mingo@kernel.org \
--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).