From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>
Subject: [GIT PULL] clockevents: 3.18 fix
Date: Wed, 19 Nov 2014 10:47:43 +0100 [thread overview]
Message-ID: <546C673F.8000502@linaro.org> (raw)
Hi Thomas,
This pull request, for timers/urgent, contains one fix for the sun4i
board where the interrupt handler was registered before the timer
itself, thus opening a window where the interrupt could be fired and
leading to an uninitialized data access.
Thanks !
-- Daniel
The following changes since commit 59aa896db80479dec29f471a7ca2b9eeeeb7d38e:
ARM/ARM64: arch-timer: fix arch_timer_probed logic (2014-10-26
20:50:00 +0100)
are available in the git repository at:
http://git.linaro.org/git-ro/people/daniel.lezcano/linux.git
clockevents/3.18-fixes
for you to fetch changes up to 6bab4a8a1888729f17f4923cc5867e4674f66333:
clockevent: sun4i: Fix race condition in the probe code (2014-11-19
10:43:51 +0100)
----------------------------------------------------------------
Maxime Ripard (1):
clockevent: sun4i: Fix race condition in the probe code
drivers/clocksource/sun4i_timer.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next reply other threads:[~2014-11-19 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 9:47 Daniel Lezcano [this message]
2014-11-19 9:49 ` [PATCH] clockevent: sun4i: Fix race condition in the probe code Daniel Lezcano
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=546C673F.8000502@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=tglx@linutronix.de \
/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.