[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpokM=5W+qAtCgurtiZvMV2A98xD_M2908Veop0pjD2-FSQ@mail.gmail.com>
Date: Sat, 14 Sep 2013 09:31:41 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: David Miller <davem@...emloft.net>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
Patch Tracking <patches@...aro.org>,
"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>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, sparclinux@...r.kernel.org
Subject: Re: [PATCH 012/228] cpufreq: sparc: call cpufreq_frequency_table_get_attr()
On 14 September 2013 03:17, David Miller <davem@...emloft.net> wrote:
> From: Viresh Kumar <viresh.kumar@...aro.org>
> Date: Fri, 13 Sep 2013 18:29:18 +0530
>
>> This exposes frequency table of driver to cpufreq core and is required for core
>> to guess what the index for a target frequency is, when it calls
>> cpufreq_frequency_table_target(). And so this driver needs to expose it.
>>
>> Cc: David S. Miller <davem@...emloft.net>
>> Cc: sparclinux@...r.kernel.org
>> Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
>
> Wait a second, later in this series you add the put_attr() call claiming
> it's a fix.
>
> But you're the one adding the "bug" here.
>
> So if you are going to add a get_attr() call you should be adding the
> necessary put_attr() call in the same patch. Otherwise this patch
> introduces a bug.
Yeah, my mistake.. It was required to be added at both places for
very few drivers and so made this mistake..
I will merge both of those patches together..
--
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