On Thu, Oct 7, 2021 at 1:26 PM Vincent Donnefort <vincent.donnefort@xxxxxxx> wrote: > > > On Thu, Oct 07, 2021 at 06:35:55PM +0800, kernel test robot wrote: > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git bleeding-edge > > head: 6cb3f7cfca6963de4f486c4bd99fdefa56f75870 > > commit: 1f39fa0dccff71d4788089b5e617229b19166867 [47/54] cpufreq: Introducing CPUFREQ_RELATION_E > > config: arm-buildonly-randconfig-r001-20211007 (attached as .config) > > compiler: arm-linux-gnueabi-gcc (GCC) 11.2.0 > > reproduce (this is a W=1 build): > > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross > > chmod +x ~/bin/make.cross > > # https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?id=1f39fa0dccff71d4788089b5e617229b19166867 > > git remote add rafael-pm https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git > > git fetch --no-tags rafael-pm bleeding-edge > > git checkout 1f39fa0dccff71d4788089b5e617229b19166867 > > # save the attached .config to linux build tree > > mkdir build_dir > > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm SHELL=/bin/bash drivers/cpufreq/ > > > > If you fix the issue, kindly add following tag as appropriate > > Reported-by: kernel test robot <lkp@xxxxxxxxx> > > > > All errors (new ones prefixed by >>): > > > > drivers/cpufreq/mediatek-cpufreq-hw.c: In function 'mtk_cpufreq_hw_fast_switch': > > >> drivers/cpufreq/mediatek-cpufreq-hw.c:112:17: error: too few arguments to function 'cpufreq_table_find_index_dl' > > 112 | index = cpufreq_table_find_index_dl(policy, target_freq); > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ > > In file included from drivers/cpufreq/mediatek-cpufreq-hw.c:7: > > include/linux/cpufreq.h:814:19: note: declared here > > 814 | static inline int cpufreq_table_find_index_dl(struct cpufreq_policy *policy, > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > Rafael, > > The issue is this patch > > cpufreq: Introducing CPUFREQ_RELATION_E > > How would you like to proceed? Do you want a v8 patch-set with the fix or just > that patch updated? Please send an incremental fix on top of the series.
