From: kernel test robot <lkp@intel.com>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [cris:scmi_transport_instance_handle_V1 5/5] drivers/firmware/arm_scmi/transports/optee.c:224:29: error: use of undeclared identifier 'mutexname'; did you mean 'putname'?
Date: Wed, 06 May 2026 16:24:43 +0800 [thread overview]
Message-ID: <202605061623.56IAmep6-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/cris/linux.git scmi_transport_instance_handle_V1
head: 13190d4c752c9adc3184690ccf035795be170fb9
commit: 13190d4c752c9adc3184690ccf035795be170fb9 [5/5] firmware: arm_scmi: optee: Rework transport probe sequence
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20260506/202605061623.56IAmep6-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260506/202605061623.56IAmep6-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/202605061623.56IAmep6-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/firmware/arm_scmi/transports/optee.c:224:29: error: use of undeclared identifier 'mutexname'; did you mean 'putname'?
224 | .mtx = __MUTEX_INITIALIZER(mutexname),
| ^~~~~~~~~
| putname
include/linux/mutex.h:83:29: note: expanded from macro '__MUTEX_INITIALIZER'
83 | __DEBUG_MUTEX_INITIALIZER(lockname) \
| ^
include/linux/mutex.h:40:14: note: expanded from macro '__DEBUG_MUTEX_INITIALIZER'
40 | , .magic = &lockname
| ^
include/linux/fs.h:2539:13: note: 'putname' declared here
2539 | extern void putname(struct filename *name);
| ^
1 error generated.
vim +224 drivers/firmware/arm_scmi/transports/optee.c
222
223 static struct scmi_optee_suppliers scmi_transport_suppliers = {
> 224 .mtx = __MUTEX_INITIALIZER(mutexname),
225 .available = INIT_ERR_PTR(-EPROBE_DEFER),
226 .th.supplier_get = scmi_optee_supplier_get,
227 .th.supplier_put = scmi_optee_supplier_put,
228 };
229
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-06 8:25 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=202605061623.56IAmep6-lkp@intel.com \
--to=lkp@intel.com \
--cc=cristian.marussi@arm.com \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox