On 28 March 2014 14:56, Jean Delvare <jdelvare@xxxxxxx> wrote: > the cbe_cpufreq_pmi and cbe-cpufreq drivers were moved and renamed, > together with their respective Kconfig symbols. In the move, > tristate CBE_CPUFREQ_PMI became bool CPU_FREQ_CBE_PMI. This makes it > impossible to build the ppc_cbe_cpufreq_pmi driver as a module, while > that was possible before the move. > > I see nothing in the commit message that would suggest that this change > was intentional. Instead I suspect this is a mistake and > CPU_FREQ_CBE_PMI was actually supposed to be a tristate. Yes, that was a mistake and it happened because I removed CBE_CPUFREQ_PMI_ENABLE completely and reused its definition for CBE_CPUFREQ_PMI and didn't notice the bool things :( -- 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
