linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [gerg-m68knommu:dt 11/14] arch/m68k/kernel/setup_no.c:78:35: error: '__dtb_start' undeclared; did you mean '__bss_start'?
@ 2025-03-19  6:57 kernel test robot
  0 siblings, 0 replies; only message in thread
From: kernel test robot @ 2025-03-19  6:57 UTC (permalink / raw)
  To: Greg Ungerer; +Cc: oe-kbuild-all, linux-m68k, uclinux-dev

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git dt
head:   0745513f96d4acbbfa7ec680d7e7a501a81a2684
commit: db44fb7b2762dd968dac8291273ab11c2f5c47df [11/14] m68k: implement a builtin devicetree for nonmmu
config: m68k-randconfig-r072-20250319 (https://download.01.org/0day-ci/archive/20250319/202503191416.7qWO7Wpv-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250319/202503191416.7qWO7Wpv-lkp@intel.com/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@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202503191416.7qWO7Wpv-lkp@intel.com/

All errors (new ones prefixed by >>):

>> make[3]: *** No rule to make target 'arch/m68k/boot/dts/mcf5208evb.dtb', needed by 'arch/m68k/boot/dts/'.
>> make[3]: *** No rule to make target 'arch/m68k/boot/dts/mcf5475evb.dtb', needed by 'arch/m68k/boot/dts/'.
   make[3]: Target 'arch/m68k/boot/dts/' not remade because of errors.
--
   In file included from arch/m68k/kernel/setup.c:5:
   arch/m68k/kernel/setup_no.c: In function 'm68k_setup_fdt':
>> arch/m68k/kernel/setup_no.c:78:35: error: '__dtb_start' undeclared (first use in this function); did you mean '__bss_start'?
     phys_addr_t fdt = (phys_addr_t) &__dtb_start;
                                      ^~~~~~~~~~~
                                      __bss_start
   arch/m68k/kernel/setup_no.c:78:35: note: each undeclared identifier is reported only once for each function it appears in
   arch/m68k/kernel/setup_no.c:81:7: error: implicit declaration of function 'early_init_dt_verify'; did you mean 'early_initcall'? [-Werror=implicit-function-declaration]
     if (!early_init_dt_verify(__va(fdt), fdt)) {
          ^~~~~~~~~~~~~~~~~~~~
          early_initcall
   arch/m68k/kernel/setup_no.c:85:2: error: implicit declaration of function 'early_init_dt_scan_nodes'; did you mean 'early_init_dt_scan_chosen_stdout'? [-Werror=implicit-function-declaration]
     early_init_dt_scan_nodes();
     ^~~~~~~~~~~~~~~~~~~~~~~~
     early_init_dt_scan_chosen_stdout
   cc1: some warnings being treated as errors


vim +78 arch/m68k/kernel/setup_no.c

    74	
    75	#ifdef CONFIG_BUILTIN_DTB
    76	static void __init m68k_setup_fdt(void)
    77	{
  > 78		phys_addr_t fdt = (phys_addr_t) &__dtb_start;
    79	
    80		pr_info("m68k generic DT machine support, FDT blob at 0x%08x\n", fdt);
    81		if (!early_init_dt_verify(__va(fdt), fdt)) {
    82			pr_err("FDT blob is bad?!\n");
    83			return;
    84		}
    85		early_init_dt_scan_nodes();
    86		unflatten_device_tree();
    87	}
    88	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2025-03-19  6:57 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-03-19  6:57 [gerg-m68knommu:dt 11/14] arch/m68k/kernel/setup_no.c:78:35: error: '__dtb_start' undeclared; did you mean '__bss_start'? kernel test robot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).