[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <481c901a-3424-4fd0-8eb3-947147dc8730@leemhuis.info>
Date: Wed, 12 Mar 2025 07:48:25 +0100
From: Thorsten Leemhuis <linux@...mhuis.info>
To: Stuart Yoder <stuart.yoder@....com>, jarkko@...nel.org
Cc: linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
lenb@...nel.org, rafael@...nel.org, jgg@...pe.ca, peterhuewe@....de,
sudeep.holla@....com, linux-integrity@...r.kernel.org,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: Build error on -next due to tpm_crb.c changes?
On 12.03.25 03:51, Stuart Yoder wrote:
> 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.
$ grep CRB kernel-aarch64-fedora.config
CONFIG_TCG_CRB=y
CONFIG_TCG_ARM_CRB_FFA=m
As I said, this was not a choice of mine, just what Fedora config
generator came up with. This of course can be adjusted, but if it did I
guess users might run into this, too.
Anyway, full .config attached. HTH. And sorry for the trouble I caused.
Ciao, Thorsten
View attachment "kernel-aarch64-fedora.config" of type "text/plain" (327978 bytes)
Powered by blists - more mailing lists