From: kernel test robot <lkp@intel.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Lee Jones <lee@kernel.org>
Subject: [lee-mfd:for-mfd-next 32/42] ld.lld: error: undefined symbol: stmpe_enable
Date: Thu, 4 Sep 2025 20:15:23 +0800 [thread overview]
Message-ID: <202509042050.mCkkZuJS-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
head: a4eb677652a5da4d8e7271c0c0c8719c39f10e36
commit: e160dd0ac8c35747a8ef74aa62c6346c2d76e644 [32/42] mfd: stmpe: Allow building as module
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20250904/202509042050.mCkkZuJS-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250904/202509042050.mCkkZuJS-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/202509042050.mCkkZuJS-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: stmpe_enable
>>> referenced by gpio-stmpe.c
>>> drivers/gpio/gpio-stmpe.o:(stmpe_gpio_probe) in archive vmlinux.a
--
>> ld.lld: error: undefined symbol: stmpe_disable
>>> referenced by gpio-stmpe.c
>>> drivers/gpio/gpio-stmpe.o:(stmpe_gpio_probe) in archive vmlinux.a
>>> referenced by gpio-stmpe.c
>>> drivers/gpio/gpio-stmpe.o:(stmpe_gpio_disable) in archive vmlinux.a
--
>> ld.lld: error: undefined symbol: stmpe_reg_read
>>> referenced by gpio-stmpe.c
>>> drivers/gpio/gpio-stmpe.o:(stmpe_dbg_show) in archive vmlinux.a
>>> referenced by gpio-stmpe.c
>>> drivers/gpio/gpio-stmpe.o:(stmpe_dbg_show) in archive vmlinux.a
>>> referenced by gpio-stmpe.c
>>> drivers/gpio/gpio-stmpe.o:(stmpe_dbg_show) in archive vmlinux.a
>>> referenced 7 more times
--
>> ld.lld: error: undefined symbol: stmpe_block_read
>>> referenced by gpio-stmpe.c
>>> drivers/gpio/gpio-stmpe.o:(stmpe_gpio_irq) in archive vmlinux.a
--
>> ld.lld: error: undefined symbol: stmpe_reg_write
>>> referenced by gpio-stmpe.c
>>> drivers/gpio/gpio-stmpe.o:(stmpe_gpio_irq) in archive vmlinux.a
>>> referenced by gpio-stmpe.c
>>> drivers/gpio/gpio-stmpe.o:(stmpe_gpio_irq) in archive vmlinux.a
>>> referenced by gpio-stmpe.c
>>> drivers/gpio/gpio-stmpe.o:(stmpe_gpio_direction_output) in archive vmlinux.a
>>> referenced 2 more times
--
>> ld.lld: error: undefined symbol: stmpe_set_altfunc
>>> referenced by gpio-stmpe.c
>>> drivers/gpio/gpio-stmpe.o:(stmpe_gpio_request) in archive vmlinux.a
--
>> ld.lld: error: undefined symbol: stmpe_set_bits
>>> referenced by gpio-stmpe.c
>>> drivers/gpio/gpio-stmpe.o:(stmpe_gpio_direction_input) in archive vmlinux.a
>>> referenced by gpio-stmpe.c
>>> drivers/gpio/gpio-stmpe.o:(stmpe_gpio_direction_output) in archive vmlinux.a
>>> referenced by gpio-stmpe.c
>>> drivers/gpio/gpio-stmpe.o:(stmpe_gpio_direction_output) in archive vmlinux.a
>>> referenced 1 more times
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-09-04 12:15 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=202509042050.mCkkZuJS-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=lee@kernel.org \
--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 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.