From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/4] clocksource: tcb_clksrc: fix setup_clkevents error path
Date: Tue, 11 Aug 2015 15:27:45 +0200 [thread overview]
Message-ID: <55C9F851.1000204@linaro.org> (raw)
In-Reply-To: <1439285884-16051-4-git-send-email-alexandre.belloni@free-electrons.com>
On 08/11/2015 11:38 AM, Alexandre Belloni wrote:
> From: Boris Brezillon <boris.brezillon@free-electrons.com>
>
> t2_clk is already disabled before request_irq(), it must not be disabled
> again.
>
> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> ---
Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
--
<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
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Boris Brezillon <boris.brezillon@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v3 3/4] clocksource: tcb_clksrc: fix setup_clkevents error path
Date: Tue, 11 Aug 2015 15:27:45 +0200 [thread overview]
Message-ID: <55C9F851.1000204@linaro.org> (raw)
In-Reply-To: <1439285884-16051-4-git-send-email-alexandre.belloni@free-electrons.com>
On 08/11/2015 11:38 AM, Alexandre Belloni wrote:
> From: Boris Brezillon <boris.brezillon@free-electrons.com>
>
> t2_clk is already disabled before request_irq(), it must not be disabled
> again.
>
> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> ---
Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
--
<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 prev parent reply other threads:[~2015-08-11 13:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 9:38 [PATCH v3 0/4] ARM: at91: Properly handle slow clock Alexandre Belloni
2015-08-11 9:38 ` Alexandre Belloni
2015-08-11 9:38 ` Alexandre Belloni
2015-08-11 9:38 ` [PATCH v3 1/4] watchdog: at91sam9: get and use " Alexandre Belloni
2015-08-11 9:38 ` Alexandre Belloni
2015-08-11 9:38 ` [PATCH v3 2/4] clocksource: atmel-st: " Alexandre Belloni
2015-08-11 9:38 ` Alexandre Belloni
2015-08-11 13:27 ` Daniel Lezcano
2015-08-11 13:27 ` Daniel Lezcano
2015-08-11 9:38 ` [PATCH v3 3/4] clocksource: tcb_clksrc: fix setup_clkevents error path Alexandre Belloni
2015-08-11 9:38 ` Alexandre Belloni
2015-08-11 13:27 ` Daniel Lezcano [this message]
2015-08-11 13:27 ` Daniel Lezcano
2015-08-11 9:38 ` [PATCH v3 4/4] misc: atmel_tclib: get and use slow clock Alexandre Belloni
2015-08-11 9:38 ` Alexandre Belloni
2015-08-11 9:38 ` Alexandre Belloni
2015-08-11 13:40 ` Daniel Lezcano
2015-08-11 13:40 ` Daniel Lezcano
2015-08-11 15:27 ` Alexandre Belloni
2015-08-11 15:27 ` Alexandre Belloni
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=55C9F851.1000204@linaro.org \
--to=daniel.lezcano@linaro.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 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.