From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] CLKDEV: return from clk_find as soon as we get maching clk
Date: Tue, 2 Mar 2010 22:01:38 +0100 [thread overview]
Message-ID: <20100302210138.GB25807@pengutronix.de> (raw)
In-Reply-To: <20100302203911.GB20675@n2100.arm.linux.org.uk>
Hello,
On Tue, Mar 02, 2010 at 08:39:11PM +0000, Russell King - ARM Linux wrote:
> On Tue, Mar 02, 2010 at 04:35:54PM +0530, Viresh KUMAR wrote:
> > clk_find function looks for clock with matching dev_id and con_id.
> > We should return from clk_find as soon as we get a clock with matching dev_id
> > and con_id. This can be done by comparing variable "match" with 3.
>
> This breaks the semantics function. Please look again at the code you're
> modifying, and ascertain whether you're changing the semantics of it,
> particularly with respect to what happens _in addition_ to returning the
> struct clk.
>
> Hint: "return p->clk" is insufficient.
I starred a the code a bit, but I don't see the problem here. match is
always <= 3 so if it is 3 in one iteration best increases to 3 and clk
isn't touched anymore. The other statements in the loop have no side
effects either.
Apart from that a while back I thought about removing
if (match == 0)
continue;
as if match is 0 the next if condition is false. I don't remember why I
didn't do it. Maybe I checked the generated code and it made no
difference.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-03-02 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 11:05 [PATCH] CLKDEV: return from clk_find as soon as we get maching clk Viresh KUMAR
2010-03-02 20:39 ` Russell King - ARM Linux
2010-03-02 21:01 ` Uwe Kleine-König [this message]
2010-03-03 19:44 ` Russell King - ARM Linux
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=20100302210138.GB25807@pengutronix.de \
--to=u.kleine-koenig@pengutronix.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).