From: Jarkko Sakkinen <jarkko@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Stuart Yoder <stuart.yoder@arm.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [linux-next:master 9090/10334] ld.lld: error: undefined symbol: tpm_crb_ffa_init
Date: Wed, 12 Mar 2025 07:57:24 +0200 [thread overview]
Message-ID: <Z9EiRDuWfPOkcjXN@kernel.org> (raw)
In-Reply-To: <Z9EhqAxJjbsUiuC_@kernel.org>
On Wed, Mar 12, 2025 at 07:54:52AM +0200, Jarkko Sakkinen wrote:
> On Wed, Mar 12, 2025 at 09:51:04AM +0800, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: eea255893718268e1ab852fb52f70c613d109b99
> > commit: 9b2015ee9b5bba20097ea1e1f4188067624f4fa3 [9090/10334] tpm_crb: add support for the Arm FF-A start method
> > config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20250312/202503120916.TnY8Xobl-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/20250312/202503120916.TnY8Xobl-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/202503120916.TnY8Xobl-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>):
> >
> > >> ld.lld: error: undefined symbol: tpm_crb_ffa_init
> > >>> referenced by tpm_crb.c
> > >>> drivers/char/tpm/tpm_crb.o:(crb_acpi_add) in archive vmlinux.a
> > --
> > >> ld.lld: error: undefined symbol: tpm_crb_ffa_start
> > >>> referenced by tpm_crb.c
> > >>> drivers/char/tpm/tpm_crb.o:(__crb_request_locality) in archive vmlinux.a
> > >>> referenced by tpm_crb.c
> > >>> drivers/char/tpm/tpm_crb.o:(__crb_relinquish_locality) in archive vmlinux.a
> > >>> referenced by tpm_crb.c
> > >>> drivers/char/tpm/tpm_crb.o:(crb_send) in archive vmlinux.a
> > >>> referenced 1 more times
> >
> > --
> > 0-DAY CI Kernel Test Service
> > https://github.com/intel/lkp-tests/wiki
>
> Stuart, I did not go through this but this does not look correct even with
> a quick peak:
>
> config TCG_ARM_CRB_FFA
> ~~~~~~~~~~~~~~~
> TCG_FTPM_FFA (and Kconfig put before TCG_FTPM_TEE)
>
>
> tristate "TPM CRB over Arm FF-A Transport"
> depends on ARM_FFA_TRANSPORT
> default y if (TCG_CRB && ARM_FFA_TRANSPORT)
> ~~~~~~~~~~~~~~~~~
> redundant given "depends on"
>
> help
> If the Arm FF-A transport is used to access the TPM say Yes.
> To compile this driver as a module, choose M here; the module
> will be called tpm_crb_ffa.
>
> So I'll drop the whole series from my tree for the moment and you'll
> have to respin.
Commit could use short summary in along the lines of:
"tpm: ftpm_ffa: <summary>"
BR, Jarkko
next prev parent reply other threads:[~2025-03-12 5:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 1:51 [linux-next:master 9090/10334] ld.lld: error: undefined symbol: tpm_crb_ffa_init kernel test robot
2025-03-12 5:54 ` Jarkko Sakkinen
2025-03-12 5:57 ` Jarkko Sakkinen [this message]
2025-03-12 15:00 ` Stuart Yoder
2025-03-12 14:57 ` Stuart Yoder
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=Z9EiRDuWfPOkcjXN@kernel.org \
--to=jarkko@kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=stuart.yoder@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