linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2] powerpc/perf: Fix IMC_MAX_PMU macro
Date: Wed, 22 Nov 2017 10:49:48 +0530	[thread overview]
Message-ID: <1d964e85-472f-9f11-e58e-23ce1c217e65@linux.vnet.ibm.com> (raw)
In-Reply-To: <87wp2j2jir.fsf@concordia.ellerman.id.au>



On Wednesday 22 November 2017 06:53 AM, Michael Ellerman wrote:
> Madhavan Srinivasan <maddy@linux.vnet.ibm.com> writes:
>
>> diff --git a/arch/powerpc/platforms/powernv/opal-imc.c b/arch/powerpc/platforms/powernv/opal-imc.c
>> index b150f4deaccf..4764e6932cb7 100644
>> --- a/arch/powerpc/platforms/powernv/opal-imc.c
>> +++ b/arch/powerpc/platforms/powernv/opal-imc.c
>> @@ -153,6 +153,22 @@ static void disable_core_pmu_counters(void)
>>   	put_online_cpus();
>>   }
>>   
>> +int get_max_nest_dev(void)
>> +{
>> +	struct device_node *node;
>> +	u32 pmu_units, type;
>> +
>> +	for_each_compatible_node(node, NULL, IMC_DTB_UNIT_COMPAT) {
>> +		if (of_property_read_u32(node, "type", &type))
>> +			continue;
>> +
>> +		if (type == IMC_TYPE_CHIP)
>> +			pmu_units++;
>> +	}
>> +
>> +	return pmu_units;
>> +}
> Breaks:
>
>    arch/powerpc/platforms/powernv/opal-imc.c:169:2: error: 'pmu_units' may be used uninitialized in this function [-Werror=maybe-uninitialized]

My bad. My cross tool also missed to catch this.
Will respin.

Maddy


>
> http://kisskb.ellerman.id.au/kisskb/head/1e59fb813346ee43be2a3a9acf4aac2815af1284/
>
> cheers
>

      reply	other threads:[~2017-11-22  5:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10 20:39 [PATCH 1/2] powerpc/perf: Fix pmu_count to count only nest imc pmus Madhavan Srinivasan
2017-11-10 20:39 ` [PATCH 2/2] powerpc/perf: Fix IMC_MAX_PMU macro Madhavan Srinivasan
2017-11-22  1:23   ` Michael Ellerman
2017-11-22  5:19     ` Madhavan Srinivasan [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=1d964e85-472f-9f11-e58e-23ce1c217e65@linux.vnet.ibm.com \
    --to=maddy@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.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).