From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-6.6 192/192] drivers/firmware/arm_scmi/tinysys.c:318: undefined reference to `scmi_protocol_register'
Date: Wed, 5 Feb 2025 16:47:50 +0800 [thread overview]
Message-ID: <202502051657.E8JYASut-lkp@intel.com> (raw)
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-6.6
head: 1b7d37693f7bd7e9f37c02d15753e16b5bac8c79
commit: f1e104ed61ffbb353b91e2a25e09f96ac805bd4c [192/192] CHROMIUM: firmware: arm_scmi: Porting tinysys_scmi driver
config: i386-buildonly-randconfig-003-20250205 (https://download.01.org/0day-ci/archive/20250205/202502051657.E8JYASut-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250205/202502051657.E8JYASut-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/202502051657.E8JYASut-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
ld: drivers/firmware/arm_scmi/tinysys.o: in function `scmi_tinysys_register':
>> drivers/firmware/arm_scmi/tinysys.c:318: undefined reference to `scmi_protocol_register'
--
>> drivers/firmware/arm_scmi/tinysys-scmi-drv.c:71:5: warning: no previous prototype for 'scmi_tinysys_notifier_fn' [-Wmissing-prototypes]
71 | int scmi_tinysys_notifier_fn(struct notifier_block *nb,
| ^~~~~~~~~~~~~~~~~~~~~~~~
vim +318 drivers/firmware/arm_scmi/tinysys.c
315
316 int scmi_tinysys_register(void)
317 {
> 318 return scmi_protocol_register(&scmi_tinysys_protocol);
319 }
320
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-05 8:48 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=202502051657.E8JYASut-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.