public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Stuart Yoder <stuart.yoder@arm.com>
To: Thorsten Leemhuis <linux@leemhuis.info>, jarkko@kernel.org
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	lenb@kernel.org, rafael@kernel.org, jgg@ziepe.ca,
	peterhuewe@gmx.de, sudeep.holla@arm.com,
	linux-integrity@vger.kernel.org,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: Build error on -next due to tpm_crb.c changes?
Date: Tue, 11 Mar 2025 21:51:49 -0500	[thread overview]
Message-ID: <635af7df-be7c-4eb1-95d7-cad26a2af787@arm.com> (raw)
In-Reply-To: <77fb9077-f598-4308-8862-6d09b23688bb@leemhuis.info>



On 3/11/25 11:51 AM, Thorsten Leemhuis wrote:
> On 11.03.25 16:53, Stuart Yoder wrote:
>> On 3/11/25 10:21 AM, Thorsten Leemhuis wrote:
>>> On 05.03.25 18:36, Stuart Yoder wrote:
>> [...]
>> So, it should not be possible on one had have
>> CONFIG_TCG_ARM_CRB_FFA being true when building tpm_crb.c
>> and false resulting in the tpm_crb_ffa.o not being
>> picked up in the build.
> 
> Many thx for the answer. Maybe Fedora's way to prepare the .config files
> (which my package builds use to be close to Fedora's official packages)
> is doing something odd/wrong. Will take a closer look and report back.

It would help to be able to see the .config to see how the relevant
config options were set.

Thanks,
Stuart


  parent reply	other threads:[~2025-03-12  2:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 17:36 [PATCH v6 0/5] Add support for the TPM FF-A start method Stuart Yoder
2025-03-05 17:36 ` [PATCH v6 1/5] tpm_crb: implement driver compliant to CRB over FF-A Stuart Yoder
2025-03-06 22:43   ` Jarkko Sakkinen
2025-03-05 17:36 ` [PATCH v6 2/5] tpm_crb: clean-up and refactor check for idle support Stuart Yoder
2025-03-05 17:36 ` [PATCH v6 3/5] ACPICA: add start method for Arm FF-A Stuart Yoder
2025-03-05 17:36 ` [PATCH v6 4/5] tpm_crb: add support for the Arm FF-A start method Stuart Yoder
2025-03-05 17:36 ` [PATCH v6 5/5] Documentation: tpm: add documentation for the CRB FF-A interface Stuart Yoder
2025-03-06 22:45 ` [PATCH v6 0/5] Add support for the TPM FF-A start method Jarkko Sakkinen
2025-03-10 11:19 ` Jarkko Sakkinen
2025-03-11 15:28   ` Sudeep Holla
2025-03-12  6:06     ` Jarkko Sakkinen
2025-03-11 15:21 ` Build error on -next due to tpm_crb.c changes? (was: Re: [PATCH v6 0/5] Add support for the TPM FF-A start method) Thorsten Leemhuis
2025-03-11 15:53   ` Build error on -next due to tpm_crb.c changes? Stuart Yoder
2025-03-11 16:51     ` Thorsten Leemhuis
2025-03-11 18:25       ` Stuart Yoder
2025-03-11 21:17         ` Sudeep Holla
2025-03-12 20:47           ` Stuart Yoder
2025-03-12  2:51       ` Stuart Yoder [this message]
2025-03-12  6:48         ` Thorsten Leemhuis
2025-03-12  6:05       ` Jarkko Sakkinen
2025-03-12  6:00   ` Build error on -next due to tpm_crb.c changes? (was: Re: [PATCH v6 0/5] Add support for the TPM FF-A start method) Jarkko Sakkinen

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=635af7df-be7c-4eb1-95d7-cad26a2af787@arm.com \
    --to=stuart.yoder@arm.com \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=peterhuewe@gmx.de \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@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