linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linux PM list <linux-pm@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: linux-next: build warning after merge of the pm tree
Date: Mon, 14 Nov 2016 14:19:33 +0530	[thread overview]
Message-ID: <8b5d3227-b5e4-c45c-3703-aa17a1584893@linux.vnet.ibm.com> (raw)
In-Reply-To: <2357318.aIcIp7uAlP@vostro.rjw.lan>

Hi Rafeal,

Good catch, I need to set lpstate_idx = gpstate_idx.
I will send a patch which fixes this commit.

Thanks Stephen for reporting it. :)

Regards
Akshay Adiga

On 11/14/2016 05:33 AM, Rafael J. Wysocki wrote:
> On Monday, November 14, 2016 10:40:09 AM Stephen Rothwell wrote:
> > Hi Rafael,
>
> Hi Stephen,
>
> > After merging the pm tree, today's linux-next build (powerpc
> > ppc64_defconfig) produced this warning:
> >
> > drivers/cpufreq/powernv-cpufreq.c: In function 'gpstate_timer_handler':
> > drivers/cpufreq/powernv-cpufreq.c:642:5: warning: 'lpstate_idx' may
> be used uninitialized in this function [-Wmaybe-uninitialized]
> >   if (gpstate_idx != gpstates->last_lpstate_idx)
> >      ^
> >
> > Introduced by commit
> >
> >   20b15b766354 ("cpufreq: powernv: Use PMCR to verify global and
> local pstate")
>
> Thanks for the notice!
>
> Akshay, any thoughts?
>
> Thanks,
> Rafael
>

  reply	other threads:[~2016-11-14  8:49 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-13 23:40 linux-next: build warning after merge of the pm tree Stephen Rothwell
2016-11-14  0:03 ` Rafael J. Wysocki
2016-11-14  8:49   ` Akshay Adiga [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-05  5:00 Stephen Rothwell
2024-02-05  5:30 ` Meng, Li (Jassmine)
2022-02-06 22:40 Stephen Rothwell
2021-10-13  6:28 Stephen Rothwell
2022-01-17 22:02 ` Stephen Rothwell
2021-03-31  0:29 Stephen Rothwell
2021-03-31  6:22 ` Vitaly Kuznetsov
2021-04-02 17:18   ` Rafael J. Wysocki
2021-02-15  0:39 Stephen Rothwell
2021-02-15 10:23 ` Andy Shevchenko
2021-02-15 10:24   ` Andy Shevchenko
2021-02-22  8:34 ` Stephen Rothwell
2021-01-27  1:43 Stephen Rothwell
2021-01-27  3:54 ` Zhang Rui
2020-11-19  0:09 Stephen Rothwell
2020-11-19 16:22 ` Andy Shevchenko
2020-09-22  8:11 Stephen Rothwell
2020-10-01  9:43 ` Stephen Rothwell
2020-10-08  9:35   ` Stephen Rothwell
2020-10-15  7:20     ` Stephen Rothwell
2020-07-30  2:55 Stephen Rothwell
2020-07-30  3:10 ` Neal Liu
2020-01-19 23:40 Stephen Rothwell
2019-10-14 23:08 Stephen Rothwell
2019-10-15  8:23 ` Andy Shevchenko
2019-10-15  9:41   ` Rafael J. Wysocki
     [not found] <201907111346291954773@zte.com.cn>
2019-07-11 12:26 ` Rafael J. Wysocki
2019-07-11  1:31 Stephen Rothwell
2019-01-23 23:45 Stephen Rothwell
2018-07-30  2:00 Stephen Rothwell
2018-07-30  7:24 ` Sakari Ailus
2018-07-30  7:30   ` jacopo mondi
2018-07-31  0:39   ` Stephen Rothwell
2018-06-08  0:30 Stephen Rothwell
2018-06-08  9:14 ` Rafael J. Wysocki
2018-04-09  1:24 Stephen Rothwell
2018-04-10  7:05 ` Rafael J. Wysocki
2014-11-17  2:44 Stephen Rothwell
2014-11-17 11:31 ` Paul Bolle
2014-11-17 23:14   ` Rafael J. Wysocki
2014-11-17 23:45     ` Paul Bolle
2014-11-18  0:34       ` Rafael J. Wysocki
2014-10-29  2:51 Stephen Rothwell
2014-10-29 14:55 ` Rafael J. Wysocki
2014-10-29 15:23   ` Fengguang Wu
2014-10-29 15:56     ` Rafael J. Wysocki

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=8b5d3227-b5e4-c45c-3703-aa17a1584893@linux.vnet.ibm.com \
    --to=akshay.adiga@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=sfr@canb.auug.org.au \
    /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).