kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Mallon <ryan@bluewatersys.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/4] arch/arm/mach-at91/clock.c: Add missing IS_ERR test
Date: Mon, 24 Jan 2011 20:38:51 +0000	[thread overview]
Message-ID: <4D3DE35B.1030102@bluewatersys.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1101242126570.3167@ask.diku.dk>

On 01/25/2011 09:28 AM, Julia Lawall wrote:
>> 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.
> 
> It seems a bit subtle, because the clk manipulated by clk_get in the call 
> of clk_get(dev, func) is not necessarily the same as the one in 
> clock_associate.  But perhaps this is the only possibility in practice?

Not sure I follow. The at91 clk_get does not modify the clk. In
at91_clock_associate we have:

	clk->function = func;
	clk->dev = dev;

and in clk_get we have:

	if (clk->function && (dev = clk->dev) &&
		strcmp(id, clk->function) = 0)
            return clk;

So at91_clock_associate sets the function for a clock, and clk_get
returns clocks based on the function association if the name lookup
fails. The only caveat to this is that the the clock function name
(clk->function) is not the same as any others clock's clk->name.

The !IS_ERR(clk_get(dev, func)) check in at91_clock_associate just
appears to check that the clock is not already associated with the given
function. We don't really need this check because we are just making the
same assignment anyway.

~Ryan

-- 
Bluewater Systems Ltd - ARM Technology Solution Centre

Ryan Mallon         		5 Amuri Park, 404 Barbadoes St
ryan@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

  reply	other threads:[~2011-01-24 20:38 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 19:55 [PATCH 0/4] Add missing IS_ERR test Julia Lawall
2011-01-24 19:55 ` [PATCH 1/4] fs/btrfs/inode.c: " Julia Lawall
2011-01-24 19:55 ` [PATCH 2/4] arch/arm/mach-at91/clock.c: " 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
2011-01-24 20:28           ` Julia Lawall
2011-01-24 20:38             ` Ryan Mallon [this message]
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 3/4] drivers/video/bf537-lq035.c: " Julia Lawall
2011-01-24 20:43   ` Mike Frysinger
2011-01-25  6:12     ` Paul Mundt
2011-01-25  8:36   ` Hennerich, Michael
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=4D3DE35B.1030102@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).