From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] Add new lower-latency C1 state take #2
Date: Mon, 16 Mar 2009 11:37:32 -0700 [thread overview]
Message-ID: <877i2piaab.fsf@deeprootsystems.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59301CC281858@dbde02.ent.ti.com> (Sanjeev Premi's message of "Sun\, 15 Mar 2009 22\:10\:29 +0530")
"Premi, Sanjeev" <premi@ti.com> writes:
[...]
>> > > +static int _cpuidle_allow_idle(struct powerdomain *pwrdm,
>> > > + struct clockdomain *clkdm)
>> > > +{
>> > > + omap2_clkdm_allow_idle(clkdm);
>> > > +}
>> > > +
>> > > +static int _cpuidle_deny_idle(struct powerdomain *pwrdm,
>> > > + struct clockdomain *clkdm)
>> > > +{
>> > > + omap2_clkdm_deny_idle(clkdm);
>> > > +}
>> > > +
>>
>> These functions don't return any value. Even the functions
>> omap2_clkdm_allow_idle() and omap2_clkdm_deny_idle() are void.
>>
>> So, the return type should be changed to void. Else complier
>> would throw warnings like:
>>
>> warning: no return statement in function returning non-void
>>
>> ~sanjeev
>>
>
> [sp] I commented on the patch without trying myself.
> The return type "int" is necessary for calls to functions
> pwrdm_for_each_clkdm().
>
> So, real solution would be to return with a value.
>
> @@ -70,12 +70,14 @@ static int _cpuidle_allow_idle(struct powerdomain *pwrdm,
> struct clockdomain *clkdm) {
> omap2_clkdm_allow_idle(clkdm);
> + return 0;
> }
>
> static int _cpuidle_deny_idle(struct powerdomain *pwrdm,
> struct clockdomain *clkdm)
> {
> omap2_clkdm_deny_idle(clkdm);
> + return 0;
> }
>
Thanks, I've merged this change into teh original patch and re-pushed
the PM branch.
Kevin
prev parent reply other threads:[~2009-03-16 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 14:02 [PATCH] Add new lower-latency C1 state Peter 'p2' De Schrijver
2009-03-13 16:19 ` [PATCH] Add new lower-latency C1 state take #2 Peter 'p2' De Schrijver
2009-03-13 22:08 ` Kevin Hilman
2009-03-15 16:16 ` Premi, Sanjeev
2009-03-15 16:40 ` Premi, Sanjeev
2009-03-16 18:37 ` Kevin Hilman [this message]
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=877i2piaab.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=premi@ti.com \
/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