All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jon Medhurst <tixy@linaro.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH] cpufreq: arm_big_little: remove compile-time dependency on BL_SWITCHER
Date: Tue, 12 May 2015 09:03:19 +0100	[thread overview]
Message-ID: <5551B3C7.80004@arm.com> (raw)
In-Reply-To: <20150512072754.GF32300@linux>



On 12/05/15 08:27, Viresh Kumar wrote:
> On 11-05-15, 12:24, Sudeep Holla wrote:
>> With the addition of switcher code, there's compile-time dependency on
>> BL_SWITCHER to get arm_big_little driver compiling on ARM64. Since ARM64
>
> The Kconfig dependency isn't on the switcher but big.LITTLE, which
> isn't defined for arm64. So, we need a bit of clarity here.
>

Right, we update accordingly.

>> @@ -562,8 +580,7 @@ int bL_cpufreq_register(struct cpufreq_arm_bL_ops *ops)
>>
>>   	arm_bL_ops = ops;
>>
>> -	ret = bL_switcher_get_enabled();
>> -	set_switching_enabled(ret);
>> +	set_switching_enabled(bL_switcher_get_enabled());
>
> This change wasn't required.
>
Right, I thought ret is not used anywhere else and might produce 
warnings, which is wrong. I will revert it back.

Regards,
Sudeep

  reply	other threads:[~2015-05-12  8:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 11:24 [PATCH] cpufreq: arm_big_little: remove compile-time dependency on BL_SWITCHER Sudeep Holla
2015-05-12  7:27 ` Viresh Kumar
2015-05-12  8:03   ` Sudeep Holla [this message]
2015-05-12  9:36     ` Sudeep Holla
2015-05-13 12:35 ` [PATCH v2] cpufreq: arm_big_little: remove compile-time dependency on BIG_LITTLE Sudeep Holla
2015-05-13 13:00   ` Viresh Kumar
2015-05-15  0:17     ` 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=5551B3C7.80004@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=tixy@linaro.org \
    --cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.