From: ryan@bluewatersys.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] arch/arm/mach-at91/clock.c: Add missing IS_ERR test
Date: Tue, 25 Jan 2011 09:11:51 +1300 [thread overview]
Message-ID: <4D3DDD07.1030809@bluewatersys.com> (raw)
In-Reply-To: <20110124200515.GA30963@albatros>
On 01/25/2011 09:05 AM, Vasiliy Kulikov wrote:
> On Mon, Jan 24, 2011 at 21:00 +0100, Julia Lawall wrote:
>> On Tue, 25 Jan 2011, Ryan Mallon wrote:
>>
>>> On 01/25/2011 08:55 AM, Julia Lawall wrote:
>>>> @@ -224,7 +224,7 @@ void __init at91_clock_associate(const char *id, struct device *dev, const char
>>>> {
>>>> struct clk *clk = clk_get(NULL, id);
>>>>
>>>> - if (!dev || !clk || !IS_ERR(clk_get(dev, func)))
>>>> + if (!dev || IS_ERR(clk) || !IS_ERR(clk_get(dev, func)))
>>>> return;
>>>
>>> I think we want:
>>>
>>> if (!dev || !clk || IS_ERR(clk) || !IS_ERR(clk_get(dev, func)))
>>> return;
>>>
>>> Since it is valid to return a NULL clk, and we don't want to try and
>>> dereference it if that is the case.
>>
>> Looking at the given defintion of clk_get, I can't see how that could
>> happen:
>
> clk_get() is defined per-architecture, sometimes it is NULL only.
Julia is correct. Some architectures can return NULL from clk_get, but I
didn't check the at91 before posting :-/. If we can't return NULL from
clk_get then we shouldn't bother checking for it. I do think we should
drop the !IS_ERR(clk_get(dev, func)) check though.
~Ryan
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon 5 Amuri Park, 404 Barbadoes St
ryan at bluewatersys.com PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com New Zealand
Phone: +64 3 3779127 Freecall: Australia 1800 148 751
Fax: +64 3 3779135 USA 1800 261 2934
next prev parent reply other threads:[~2011-01-24 20:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1295898922-18822-1-git-send-email-julia@diku.dk>
2011-01-24 19:55 ` [PATCH 2/4] arch/arm/mach-at91/clock.c: Add missing IS_ERR test Julia Lawall
2011-01-24 19:56 ` Ryan Mallon
2011-01-24 20:00 ` Julia Lawall
2011-01-24 20:05 ` Vasiliy Kulikov
2011-01-24 20:09 ` Julia Lawall
2011-01-24 20:14 ` Vasiliy Kulikov
2011-01-25 10:33 ` walter harms
2011-01-25 10:43 ` Russell King - ARM Linux
2011-01-25 11:12 ` walter harms
2011-01-25 11:17 ` Russell King - ARM Linux
2011-01-25 11:18 ` Julia Lawall
2011-01-25 11:26 ` Russell King - ARM Linux
2011-01-25 11:31 ` Julia Lawall
2011-01-24 20:11 ` Ryan Mallon [this message]
2011-01-24 20:28 ` Julia Lawall
2011-01-24 20:38 ` Ryan Mallon
2011-01-24 21:01 ` Julia Lawall
2011-01-24 21:06 ` Ryan Mallon
2011-01-24 21:31 ` Julia Lawall
2011-01-24 21:51 ` Ryan Mallon
2011-01-24 23:23 ` Russell King - ARM Linux
2011-01-25 1:44 ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-25 6:12 ` Julia Lawall
2011-01-25 17:23 ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-24 19:55 ` [PATCH 4/4] arch/arm/mach-omap2/smartreflex.c: " Julia Lawall
2011-01-24 21:24 ` Kevin Hilman
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=4D3DDD07.1030809@bluewatersys.com \
--to=ryan@bluewatersys.com \
--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).