From: kernel test robot <lkp@intel.com>
To: Sven Peter <sven@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [sven:efi-psci 3/6] arch/arm64/kernel/setup.c:323:9: error: implicit declaration of function 'arm64_efi_init'; did you mean 'arm64_rsi_init'?
Date: Sun, 05 Jul 2026 17:50:53 +0800 [thread overview]
Message-ID: <202607051752.5tObEBmE-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sven/linux.git efi-psci
head: f3e5c7a4c95dadd837bde2519a6226b5cd610415
commit: c11e5fb532e28ab8f8b418760df31ac7bea7e0ba [3/6] arm64/efi: Add and parse custom PSCI EFI configuration table
config: arm64-allnoconfig (https://download.01.org/0day-ci/archive/20260705/202607051752.5tObEBmE-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260705/202607051752.5tObEBmE-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/202607051752.5tObEBmE-lkp@intel.com/
All errors (new ones prefixed by >>):
arch/arm64/kernel/setup.c: In function 'setup_arch':
>> arch/arm64/kernel/setup.c:323:9: error: implicit declaration of function 'arm64_efi_init'; did you mean 'arm64_rsi_init'? [-Wimplicit-function-declaration]
323 | arm64_efi_init();
| ^~~~~~~~~~~~~~
| arm64_rsi_init
vim +323 arch/arm64/kernel/setup.c
280
281 void __init __no_sanitize_address setup_arch(char **cmdline_p)
282 {
283 setup_initial_init_mm(_text, _etext, _edata, _end);
284
285 *cmdline_p = boot_command_line;
286
287 kaslr_init();
288
289 early_fixmap_init();
290 early_ioremap_init();
291
292 setup_machine_fdt(__fdt_pointer);
293
294 /*
295 * Initialise the static keys early as they may be enabled by the
296 * cpufeature code and early parameters.
297 */
298 jump_label_init();
299 parse_early_param();
300
301 dynamic_scs_init();
302
303 /*
304 * The primary CPU enters the kernel with all DAIF exceptions masked.
305 *
306 * We must unmask Debug and SError before preemption or scheduling is
307 * possible to ensure that these are consistently unmasked across
308 * threads, and we want to unmask SError as soon as possible after
309 * initializing earlycon so that we can report any SErrors immediately.
310 *
311 * IRQ and FIQ will be unmasked after the root irqchip has been
312 * detected and initialized.
313 */
314 local_daif_restore(DAIF_PROCCTX_NOIRQ);
315
316 /*
317 * TTBR0 is only used for the identity mapping at this stage. Make it
318 * point to zero page to avoid speculatively fetching new entries.
319 */
320 cpu_uninstall_idmap();
321
322 xen_early_init();
> 323 arm64_efi_init();
324
325 if (!efi_enabled(EFI_BOOT)) {
326 if ((u64)_text % MIN_KIMG_ALIGN)
327 pr_warn(FW_BUG "Kernel image misaligned at boot, please fix your bootloader!");
328 WARN_TAINT(mmu_enabled_at_boot, TAINT_FIRMWARE_WORKAROUND,
329 FW_BUG "Booted with MMU enabled!");
330 }
331
332 arm64_memblock_init();
333
334 paging_init();
335
336 acpi_table_upgrade();
337
338 /* Parse the ACPI tables for possible boot-time configuration */
339 acpi_boot_table_init();
340
341 if (acpi_disabled)
342 unflatten_device_tree();
343
344 bootmem_init();
345
346 kasan_init();
347
348 request_standard_resources();
349
350 early_ioremap_reset();
351
352 if (acpi_disabled)
353 psci_dt_init();
354 else
355 psci_acpi_init();
356
357 arm64_rsi_init();
358
359 init_bootcpu_ops();
360 smp_init_cpus();
361 smp_build_mpidr_hash();
362
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-05 9:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202607051752.5tObEBmE-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sven@kernel.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.