[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohponphVhZ3T1HD2AfhPBUn9SfQyrqdbvW3bEJFzRdKF2i0Q@mail.gmail.com>
Date: Thu, 21 Nov 2013 21:24:02 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Lan Tianyu <tianyu.lan@...el.com>,
"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V2] Cpufreq: Make governor data on nonboot cpus across
system suspend/resume
On 21 November 2013 20:13, Rafael J. Wysocki <rjw@...ysocki.net> wrote:
>> - if (((event == CPUFREQ_GOV_POLICY_INIT) && ret) ||
>
> The inner parens are not necessary.
>
>> - ((event == CPUFREQ_GOV_POLICY_EXIT) && !ret))
>> + if ((event == CPUFREQ_GOV_POLICY_INIT) && ret) {
>
> Same here.
>
>> + module_put(policy->governor->owner);
>> + if (ret == -EALREADY)
>> + return 0;
>> + } else if ((event == CPUFREQ_GOV_POLICY_EXIT) && !ret) {
>
> Same here.
Logically, yes you are correct. But probably its better for readability to
get these even if you know precedence is going to take care of our
expression..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists