From: stigge@antcom.de (stigge at antcom.de)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 6/7] ARM: LPC32xx: clock.c: warning fix
Date: Thu, 2 Feb 2012 20:19:47 +0100 [thread overview]
Message-ID: <1328210388-21296-6-git-send-email-stigge@antcom.de> (raw)
In-Reply-To: <1328210388-21296-1-git-send-email-stigge@antcom.de>
This patch removes the debug warning on local_clk_disable() as done in Kevin
Wells' driver update
Signed-off-by: Roland Stigge <stigge@antcom.de>
Acked-by: Wolfram Sang <w.sang@pengutronix.de>
Tested-by: Wolfram Sang <w.sang@pengutronix.de>
diff --git a/arch/arm/mach-lpc32xx/clock.c b/arch/arm/mach-lpc32xx/clock.c
index d527288..0606a63 100644
--- a/arch/arm/mach-lpc32xx/clock.c
+++ b/arch/arm/mach-lpc32xx/clock.c
@@ -904,8 +904,6 @@ static inline void clk_unlock(void)
static void local_clk_disable(struct clk *clk)
{
- WARN_ON(clk->usecount == 0);
-
/* Don't attempt to disable clock if it has no users */
if (clk->usecount > 0) {
clk->usecount--;
next prev parent reply other threads:[~2012-02-02 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 19:19 [PATCH v3 1/7] ARM: LPC32xx: Added lpc32xx_defconfig stigge at antcom.de
2012-02-02 19:19 ` [PATCH v3 2/7] ARM: LPC32XX: Remove broken non-static declaration stigge at antcom.de
2012-02-02 19:19 ` [PATCH v3 3/7] ARM: LPC32xx: clock.c: Missing header file stigge at antcom.de
2012-02-02 19:19 ` [PATCH v3 4/7] ARM: LPC32xx: clock.c: jiffies wrapping stigge at antcom.de
2012-02-02 19:19 ` [PATCH v3 5/7] ARM: LPC32xx: clock.c: Clock registration fixes stigge at antcom.de
2012-02-02 19:19 ` stigge at antcom.de [this message]
2012-02-02 19:19 ` [PATCH v3 7/7] ARM: LPC32xx: clock.c: Fix mutex lock issues stigge at antcom.de
2012-02-02 21:23 ` [PATCH v3 1/7] ARM: LPC32xx: Added lpc32xx_defconfig Wolfram Sang
2012-02-02 21:52 ` Kevin Wells
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=1328210388-21296-6-git-send-email-stigge@antcom.de \
--to=stigge@antcom.de \
--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).