Re: [PATCH v2 2/5] mips: bmips: rework and cache CBR addr handling

[Christian Marangi]

On Thu, May 09, 2024 at 07:13:16AM +0800, kernel test robot wrote:
> Hi Christian,
> 
> kernel test robot noticed the following build errors:
> 
> [auto build test ERROR on robh/for-next]
> [also build test ERROR on linus/master v6.9-rc7 next-20240508]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
> 
> url:    https://github.com/intel-lab-lkp/linux/commits/Christian-Marangi/mips-bmips-BCM6358-make-sure-CBR-is-correctly-set/20240504-052513
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
> patch link:    https://lore.kernel.org/r/20240503212139.5811-3-ansuelsmth%40gmail.com
> patch subject: [PATCH v2 2/5] mips: bmips: rework and cache CBR addr handling
> config: mips-bcm63xx_defconfig (https://download.01.org/0day-ci/archive/20240509/202405090546.iqx9FAqu-lkp@xxxxxxxxx/config)
> compiler: mips-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240509/202405090546.iqx9FAqu-lkp@xxxxxxxxx/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@xxxxxxxxx>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202405090546.iqx9FAqu-lkp@xxxxxxxxx/
> 
> All errors (new ones prefixed by >>):
> 
>    mips-linux-ld: arch/mips/kernel/smp-bmips.o: in function `bmips_ebase_setup':
> >> smp-bmips.c:(.text+0x114): undefined reference to `bmips_cbr_addr'
> >> mips-linux-ld: smp-bmips.c:(.text+0x118): undefined reference to `bmips_cbr_addr'
>    mips-linux-ld: arch/mips/kernel/smp-bmips.o: in function `bmips_cpu_setup':
>    smp-bmips.c:(.text+0x1a4): undefined reference to `bmips_cbr_addr'
>    mips-linux-ld: smp-bmips.c:(.text+0x1b4): undefined reference to `bmips_cbr_addr'
>

This is caused by legacy brcm47xx and brcm63xx target. v4 will have this
fixed (and I will drop the ACK since I moved code around)

-- 
	Ansuel