From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: davinci: fix a problematic usage of WARN()
Date: Wed, 25 Nov 2015 21:28:43 +0100 [thread overview]
Message-ID: <19146462.9tlorCPL8k@wuerfel> (raw)
In-Reply-To: <201511260435.1AHQOCP1%fengguang.wu@intel.com>
On Thursday 26 November 2015 04:21:09 kbuild test robot wrote:
> 386 aemif = clk_get(&dm355evm_dm9000.dev, "aemif");
> > 387 if (!WARN(IS_ERR(aemif)), "unable to get AEMIF clock\n"))
> 388 clk_prepare_enable(aemif);
> 389
>
That is an extra ')' after aemif.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: kbuild test robot <lkp@intel.com>,
Geliang Tang <geliangtang@163.com>,
Russell King <linux@arm.linux.org.uk>,
Kevin Hilman <khilman@deeprootsystems.com>,
Sekhar Nori <nsekhar@ti.com>,
linux-kernel@vger.kernel.org, kbuild-all@01.org
Subject: Re: [PATCH v2] ARM: davinci: fix a problematic usage of WARN()
Date: Wed, 25 Nov 2015 21:28:43 +0100 [thread overview]
Message-ID: <19146462.9tlorCPL8k@wuerfel> (raw)
In-Reply-To: <201511260435.1AHQOCP1%fengguang.wu@intel.com>
On Thursday 26 November 2015 04:21:09 kbuild test robot wrote:
> 386 aemif = clk_get(&dm355evm_dm9000.dev, "aemif");
> > 387 if (!WARN(IS_ERR(aemif)), "unable to get AEMIF clock\n"))
> 388 clk_prepare_enable(aemif);
> 389
>
That is an extra ')' after aemif.
Arnd
next prev parent reply other threads:[~2015-11-25 20:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 13:12 [PATCH 1/7] drm/msm/mdp: fix a problematic usage of WARN_ON() Geliang Tang
2015-11-25 13:12 ` [PATCH 2/7] drm/vmwgfx: " Geliang Tang
2015-11-25 13:12 ` [PATCH 3/7] iio: " Geliang Tang
2015-11-25 13:12 ` [PATCH 4/7] iwlwifi: fix a problematic usage of WARN_ON_ONCE() Geliang Tang
2015-11-25 13:12 ` Geliang Tang
2015-11-25 13:12 ` [PATCH 5/7] vfio: fix a problematic usage of WARN() Geliang Tang
2015-11-25 13:35 ` Alex Williamson
2015-11-25 13:47 ` [PATCH 4/7] iwlwifi: fix a problematic usage of WARN_ON_ONCE() Grumbach, Emmanuel
2015-11-25 13:14 ` [PATCH 3/7] iio: fix a problematic usage of WARN_ON() Lars-Peter Clausen
2015-11-25 15:50 ` [PATCH 2/7] drm/vmwgfx: " Sinclair Yeh
2015-11-26 14:51 ` Thomas Hellstrom
2015-11-26 14:51 ` Thomas Hellstrom
2015-11-25 13:12 ` [PATCH 6/7] ARM: davinci: fix a problematic usage of WARN() Geliang Tang
2015-11-25 13:12 ` Geliang Tang
2015-11-25 13:12 ` [PATCH 7/7] powerpc: " Geliang Tang
2015-11-26 5:25 ` Michael Ellerman
2015-11-25 13:39 ` [PATCH 6/7] ARM: davinci: " Arnd Bergmann
2015-11-25 13:39 ` Arnd Bergmann
2015-11-25 14:13 ` [PATCH v2] " Geliang Tang
2015-11-25 14:13 ` Geliang Tang
2015-11-25 20:21 ` kbuild test robot
2015-11-25 20:21 ` kbuild test robot
2015-11-25 20:28 ` Arnd Bergmann [this message]
2015-11-25 20:28 ` Arnd Bergmann
2015-11-26 0:35 ` [PATCH v3] " Geliang Tang
2015-11-26 0:35 ` Geliang Tang
2015-12-15 9:58 ` Sekhar Nori
2015-12-15 9:58 ` Sekhar Nori
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=19146462.9tlorCPL8k@wuerfel \
--to=arnd@arndb.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 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.