From: kernel test robot <lkp@intel.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [sudeep-holla:b4/plat2faux_dev 4/9] drivers/char/hw_random/arm_smccc_trng.c:113:56: error: use of undeclared identifier 'smccc_trng_available'; did you mean 'smccc_trng_probe'?
Date: Wed, 19 Mar 2025 06:45:43 +0800 [thread overview]
Message-ID: <202503190825.mKnUVJbM-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git b4/plat2faux_dev
head: 14159d6574e30c1adeaa3460bd0abfae968987b2
commit: 870bdacafb24f3de9a81a35fc434862313f99ec8 [4/9] hwrng: arm-smccc-trng - transition to the faux device interface
config: arm-randconfig-002-20250319 (https://download.01.org/0day-ci/archive/20250319/202503190825.mKnUVJbM-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 87916f8c32ebd8e284091db9b70339df57fd1e90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250319/202503190825.mKnUVJbM-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/202503190825.mKnUVJbM-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/char/hw_random/arm_smccc_trng.c:113:56: error: use of undeclared identifier 'smccc_trng_available'; did you mean 'smccc_trng_probe'?
113 | module_faux_driver(smccc_trng, smccc_trng_probe, NULL, smccc_trng_available);
| ^~~~~~~~~~~~~~~~~~~~
| smccc_trng_probe
include/linux/device/faux.h:116:49: note: expanded from macro 'module_faux_driver'
116 | faux_device_unregister, __faux_devname, __init_condition)
| ^
include/linux/device/driver.h:260:36: note: expanded from macro 'module_driver'
260 | return __register(&(__driver) , ##__VA_ARGS__); \
| ^
include/linux/device/faux.h:99:32: note: expanded from macro 'faux_device_register'
99 | &faux_devname##_ops, init_condition)
| ^
drivers/char/hw_random/arm_smccc_trng.c:99:12: note: 'smccc_trng_probe' declared here
99 | static int smccc_trng_probe(struct faux_device *fdev)
| ^
1 error generated.
vim +113 drivers/char/hw_random/arm_smccc_trng.c
112
> 113 module_faux_driver(smccc_trng, smccc_trng_probe, NULL, smccc_trng_available);
114
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-18 22:46 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=202503190825.mKnUVJbM-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sudeep.holla@arm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox