From: KernelCI bot <bot@kernelci.org>
To: kernelci-results@groups.io
Cc: regressions@lists.linux.dev, linux-next@vger.kernel.org
Subject: [REGRESSION] next/master: (build)‘tpm_tis_resume’ undeclared here (not in a function); did you mean ...
Date: Mon, 14 Sep 2026 17:59:03 -0000 [thread overview]
Message-ID: <178940874287.1087.18054581149136757738@kernelci.org> (raw)
New build issue found on next/master:
---
‘tpm_tis_resume’ undeclared here (not in a function); did you mean ‘tpm_tis_remove’? in drivers/char/tpm/tpm_tis.o (drivers/char/tpm/tpm_tis.c) [logspec:kbuild,kbuild.compiler.error]
---
Log excerpt:
=====================================================
/tmp/kci/linux/drivers/char/tpm/tpm_tis.c:249:61: error: ‘tpm_tis_resume’ undeclared here (not in a function); did you mean ‘tpm_tis_remove’?
249 | static DEFINE_SIMPLE_DEV_PM_OPS(tpm_tis_pm, tpm_pm_suspend, tpm_tis_resume);
| ^~~~~~~~~~~~~~
/tmp/kci/linux/include/linux/util_macros.h:136:44: note: in definition of macro ‘PTR_IF’
136 | #define PTR_IF(cond, ptr) ((cond) ? (ptr) : NULL)
| ^~~
/tmp/kci/linux/include/linux/pm.h:316:19: note: in expansion of macro ‘pm_sleep_ptr’
316 | .resume = pm_sleep_ptr(resume_fn), \
| ^~~~~~~~~~~~
/tmp/kci/linux/include/linux/pm.h:375:9: note: in expansion of macro ‘SYSTEM_SLEEP_PM_OPS’
375 | SYSTEM_SLEEP_PM_OPS(suspend_fn, resume_fn) \
| ^~~~~~~~~~~~~~~~~~~
/tmp/kci/linux/include/linux/pm.h:417:9: note: in expansion of macro ‘_DEFINE_DEV_PM_OPS’
417 | _DEFINE_DEV_PM_OPS(name, suspend_fn, resume_fn, NULL, NULL, NULL)
| ^~~~~~~~~~~~~~~~~~
/tmp/kci/linux/drivers/char/tpm/tpm_tis.c:249:8: note: in expansion of macro ‘DEFINE_SIMPLE_DEV_PM_OPS’
249 | static DEFINE_SIMPLE_DEV_PM_OPS(tpm_tis_pm, tpm_pm_suspend, tpm_tis_resume);
| ^~~~~~~~~~~~~~~~~~~~~~~~
=====================================================
When fixing this issue, please attribute this report according to the
patch submission rules:
Reported-by: kernelci.org bot <bot@kernelci.org>
Link: https://lore.kernel.org/all/178940874287.1087.18054581149136757738@kernelci.org/
For complete logs and details about the environment used, see the issue
on the KernelCI dashboard:
- dashboard: https://d.kernelci.org/i/maestro:70dc580f14443e704913c358990be2bc69fa5c28
- giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
- commit HEAD: 1a1de54f7369cd2b5bac0f265910e60ad3a6b4c3
- tags: next-20260914
# Builds where the incident occurred:
## x86_64_defconfig+allnoconfig+x86-board on (x86_64):
- compiler: gcc-14
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6aa828c820239ade90355cb6
#regzbot introduced: 68142f986ff04b2b70b31db00f719bf690f64a9a..1a1de54f7369cd2b5bac0f265910e60ad3a6b4c3
#regzbot link: https://d.kernelci.org/i/maestro:70dc580f14443e704913c358990be2bc69fa5c28
#kernelci issue maestro:70dc580f14443e704913c358990be2bc69fa5c28
--
This is an experimental report format. Please send feedback in!
Talk to us at kernelci@lists.linux.dev
Made with love by the KernelCI team - https://kernelci.org
next reply other threads:[~2026-09-14 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 17:59 KernelCI bot [this message]
2026-09-18 15:28 ` [REGRESSION] next/master: (build)‘tpm_tis_resume’ undeclared here (not in a function); did you mean Thorsten Leemhuis
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=178940874287.1087.18054581149136757738@kernelci.org \
--to=bot@kernelci.org \
--cc=kernelci-results@groups.io \
--cc=kernelci@lists.linux.dev \
--cc=linux-next@vger.kernel.org \
--cc=regressions@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