Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Stuart Yoder <stuart.yoder@arm.com>
To: Jarkko Sakkinen <jarkko@kernel.org>, kernel test robot <lkp@intel.com>
Cc: 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 10:00:43 -0500	[thread overview]
Message-ID: <1f74fbf3-4b51-4f6e-b062-51a495fb17cc@arm.com> (raw)
In-Reply-To: <Z9EiRDuWfPOkcjXN@kernel.org>


>> 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>"

It really isn't fTPM specific, the FF-A based TPM service could act as a
proxy to a discrete TPM chip.  But, perhaps: ffa_tpm ?

Thanks,
Stuart


  reply	other threads:[~2025-03-12 15:00 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
2025-03-12 15:00     ` Stuart Yoder [this message]
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=1f74fbf3-4b51-4f6e-b062-51a495fb17cc@arm.com \
    --to=stuart.yoder@arm.com \
    --cc=jarkko@kernel.org \
    --cc=lkp@intel.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