From: Heikki Orsila <shd@zakalwe.fi>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-pm@lists.osdl.org, linux-kernel@vger.kernel.org,
ext-Tuukka.Tikkanen@nokia.com
Subject: Re: [RFC] OMAP1 PM Core, PM Core Implementation 2/2
Date: Sun, 1 Oct 2006 20:32:52 +0300 [thread overview]
Message-ID: <20061001173252.GB24539@zakalwe.fi> (raw)
In-Reply-To: <20061001171032.GE2254@elf.ucw.cz>
On Sun, Oct 01, 2006 at 07:10:32PM +0200, Pavel Machek wrote:
> On Sun 2006-10-01 18:22:28, Heikki Orsila wrote:
> > Some nitpicking about the patch follows..
> >
> > On Sat, Sep 30, 2006 at 02:24:35AM +0400, Eugeny S. Mints wrote:
> > > +static long
> > > +get_vtg(const char *vdomain)
> > > +{
> > > + long ret = 0;
> >
> > Unnecessary initialisation.
>
> No, sorry.
In get_vtg(), if VOLTAGE_FRAMEWORK is defined then
ret = vtg_get_voltage(v);
is the first user. If VOLTAGE_FRAMEWORK is not defined, the first user is:
ret = vtg_get_voltage(&vhandle);
Then "return ret;" follows. I cannot see a path where
pre-initialisation of ret does anything useful. If someone removed the
#else part, the compiler would bark.
>
> > > +static long
> > > +set_vtg(const char *vdomain, int val)
> > > +{
> > > + long ret = 0;
> >
> > here too.
>
> Wrong again. automatic variables are not zero initialized.
My bad, this was a mistake. If VOLTAGE_FRAMEWORK is not defined, ret
must be initialised. (the compiler would have noticed this one :-)
>> 'int i = 0;' happens in many functions.
for example, omap_pm_create_point() does this.
- Heikki
next prev parent reply other threads:[~2006-10-01 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 22:24 [RFC] OMAP1 PM Core, PM Core Implementation 2/2 Eugeny S. Mints
2006-10-01 15:22 ` Heikki Orsila
2006-10-01 17:10 ` [linux-pm] " Pavel Machek
2006-10-01 17:32 ` Heikki Orsila [this message]
2006-10-01 17:37 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-10-02 19:19 [linux-pm] " Scott E. Preece
2006-10-04 21:25 ` Pavel Machek
2006-10-04 21:33 Scott E. Preece
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=20061001173252.GB24539@zakalwe.fi \
--to=shd@zakalwe.fi \
--cc=ext-Tuukka.Tikkanen@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
/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