From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android17-6.18 0/1] drivers/android/binder.c:7389:2: error: call to undeclared function 'unload_binderfs'; ISO C99 and later do not support implicit function declarations
Date: Sat, 17 Jan 2026 18:53:27 +0800 [thread overview]
Message-ID: <202601171842.FXaePKaa-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android17-6.18
head: ba857eb99ec955367580dc1c301b326e13ef6524
commit: 42393aa5693a216b395461b4edcf1ba46526b64e [0/1] ANDROID: binder: support loading both drivers at the same time
config: x86_64-buildonly-randconfig-004-20260117 (https://download.01.org/0day-ci/archive/20260117/202601171842.FXaePKaa-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260117/202601171842.FXaePKaa-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/202601171842.FXaePKaa-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/android/binder.c:7389:2: error: call to undeclared function 'unload_binderfs'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
7389 | unload_binderfs();
| ^
drivers/android/binder.c:7389:2: note: did you mean 'init_binderfs'?
drivers/android/binder_internal.h:103:26: note: 'init_binderfs' declared here
103 | static inline int __init init_binderfs(void)
| ^
1 error generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for I2C_K1
Depends on [n]: I2C [=y] && HAS_IOMEM [=y] && (ARCH_SPACEMIT || COMPILE_TEST [=y]) && OF [=n]
Selected by [m]:
- MFD_SPACEMIT_P1 [=m] && HAS_IOMEM [=y] && (ARCH_SPACEMIT || COMPILE_TEST [=y]) && I2C [=y]
vim +/unload_binderfs +7389 drivers/android/binder.c
7385
7386 void binder_unload_builtin(void)
7387 {
7388 genl_unregister_family(&binder_nl_family);
> 7389 unload_binderfs();
7390 debugfs_remove_recursive(binder_debugfs_dir_entry_root);
7391 binder_alloc_shrinker_exit();
7392 binder_remove_trace_events(THIS_MODULE);
7393 }
7394
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-17 10:53 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=202601171842.FXaePKaa-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.