[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpokFiuP0JFu0seOFL8PQXSE9dv+NxypKzRgUjq0wYMvw6g@mail.gmail.com>
Date: Tue, 8 Apr 2014 10:59:52 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Chen Gang <gang.chen.5i5j@...il.com>
Cc: Guan Xuetao <gxt@...c.pku.edu.cn>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
stable@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] drivers:cpufreq:unicore32: fix typo issue for 'clk'
On 8 April 2014 10:09, Chen Gang <gang.chen.5i5j@...il.com> wrote:
> OK, I will/should try within this week, thanks.
Rafael has already applied this patch and has mentioned stable in
'Cc:' field. And it looks it will be applied automatically and you don't
need to do anything now :)
commit b4ddad95020e65cfbbf9aee63d3bcdf682794ade
Author: Chen Gang <gang.chen.5i5j@...il.com>
Date: Mon Apr 7 20:04:21 2014 +0800
cpufreq: unicore32: fix typo issue for 'clk'
Need use 'clk' instead of 'mclk', which is the original removed local
variable.
The related original commit:
"652ed95 cpufreq: introduce cpufreq_generic_get() routine"
The related error with allmodconfig for unicore32:
CC drivers/cpufreq/unicore2-cpufreq.o
drivers/cpufreq/unicore2-cpufreq.c: In function 'ucv2_target':
drivers/cpufreq/unicore2-cpufreq.c:48: error: 'struct
cpufreq_policy' has no member named 'mclk'
make[2]: *** [drivers/cpufreq/unicore2-cpufreq.o] Error 1
make[1]: *** [drivers/cpufreq] Error 2
make: *** [drivers] Error 2
Fixes: 652ed95d5fa6 (cpufreq: introduce cpufreq_generic_get() routine)
Signed-off-by: Chen Gang <gang.chen.5i5j@...il.com>
Acked-by: Viresh Kumar <viresh.kumar@...aro.org>
Cc: 3.14+ <stable@...r.kernel.org> # 3.14+
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
--
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