From: Thorsten Leemhuis <regressions@leemhuis.info>
To: kernelci@lists.linux.dev, kernelci-results@groups.io
Cc: regressions@lists.linux.dev, linux-next@vger.kernel.org
Subject: Re: [REGRESSION] next/master: (build)‘tpm_tis_resume’ undeclared here (not in a function); did you mean ...
Date: Fri, 18 Sep 2026 17:28:39 +0200 [thread overview]
Message-ID: <5d600227-0396-4e4f-bfcd-8aa5bbb3f548@leemhuis.info> (raw)
In-Reply-To: <178940874287.1087.18054581149136757738@kernelci.org>
On 9/14/26 19:59, KernelCI bot wrote:
> 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]
I believe this should be fixed by an updated version of the patch "tpm:
use DEFINE_SIMPLE_DEV_PM_OPS and pm_sleep_ptr()" that landed in -next
today (that hit the list shortly after this was posted, just took some
time to land apparently).
Ciao, Thorsten
#regzbot resolved: fixed by a updated patch
prev parent reply other threads:[~2026-09-18 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 17:59 [REGRESSION] next/master: (build)‘tpm_tis_resume’ undeclared here (not in a function); did you mean KernelCI bot
2026-09-18 15:28 ` Thorsten Leemhuis [this message]
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=5d600227-0396-4e4f-bfcd-8aa5bbb3f548@leemhuis.info \
--to=regressions@leemhuis.info \
--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