From: kernel test robot <lkp@intel.com>
To: Greg Ungerer <gerg@linux-m68k.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-m68k@lists.linux-m68k.org,
uclinux-dev@uclinux.org
Subject: [gerg-m68knommu:dt 12/14] arch/m68k/kernel/setup_mm.c:211:35: error: '__dtb_start' undeclared; did you mean '__bss_start'?
Date: Tue, 19 May 2026 20:25:21 +0800 [thread overview]
Message-ID: <202605192049.GzCMNtkl-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git dt
head: 3173490642db7ab3c9f15b139b19a633a2ac2d5e
commit: c9921b3e98eab8277d9aa71cc084cc821fd14213 [12/14] m68k: implement a builtin devicetree for mm targets
config: m68k-randconfig-r051-20260519 (https://download.01.org/0day-ci/archive/20260519/202605192049.GzCMNtkl-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/20260519/202605192049.GzCMNtkl-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/202605192049.GzCMNtkl-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/m68k/kernel/setup.c:3:
arch/m68k/kernel/setup_mm.c: In function 'm68k_setup_fdt':
>> arch/m68k/kernel/setup_mm.c:211: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_mm.c:211:35: note: each undeclared identifier is reported only once for each function it appears in
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for OF_EARLY_FLATTREE
Depends on [n]: OF [=n]
Selected by [y]:
- BUILTIN_DTB [=y]
vim +211 arch/m68k/kernel/setup_mm.c
207
208 #ifdef CONFIG_BUILTIN_DTB
209 static void __init m68k_setup_fdt(void)
210 {
> 211 phys_addr_t fdt = (phys_addr_t) &__dtb_start;
212
213 pr_info("m68k generic DT machine support, FDT blob at 0x%08x\n", fdt);
214 if (!early_init_dt_verify(__va(fdt), fdt)) {
215 pr_err("FDT blob is bad?!\n");
216 return;
217 }
218 early_init_dt_scan_nodes();
219 unflatten_device_tree();
220 }
221
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-05-19 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 12:25 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-19 1:53 [gerg-m68knommu:dt 12/14] arch/m68k/kernel/setup_mm.c:211:35: error: '__dtb_start' undeclared; did you mean '__bss_start'? kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202605192049.GzCMNtkl-lkp@intel.com \
--to=lkp@intel.com \
--cc=gerg@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=uclinux-dev@uclinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.