Around Tue 13 Aug 2013 19:00:22 +0530 or thereabout, Viresh Kumar wrote: > On 13 August 2013 14:39, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote: >> Yes, that's what.. That generic routine can be used instead of your .verify().. > > So here is a patch for that which I will include in my original series. It uses > functions from this patch: > > http://www.kernelhub.org/?msg=309940&p=2 Great. Is there anything left for the at32ap cpufreq driver? > -----------x-------------------x--------------------- > > commit e02892f73f8f669b265310e51a677c7253e32389 > Author: Viresh Kumar <viresh.kumar@xxxxxxxxxx> > Date: Fri Aug 9 12:05:56 2013 +0530 > > cpufreq: at32ap: Use generic cpufreq routines > > Most of the CPUFreq drivers do similar things in .exit() and > .verify() routines > and .attr. So its better if we have generic routines for them > which can be used > by cpufreq drivers then. > > This patch uses these generic routines for this driver. > > Cc: Hans-Christian Egtvedt <egtvedt@xxxxxxxxxxxx> > Signed-off-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx> Acked-by: Hans-Christian Egtvedt <egtvedt@xxxxxxxxxxxx> > --- > drivers/cpufreq/at32ap-cpufreq.c | 12 +----------- > 1 file changed, 1 insertion(+), 11 deletions(-) <snipp diff> -- mvh Hans-Christian Egtvedt -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
