mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Leonard Göhrs" <l.goehrs@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] tpm2-tss: install fapi-config.json
Date: Mon, 22 Sep 2025 13:04:19 +0200	[thread overview]
Message-ID: <20250922110419.2076199-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250917110808.167491-2-l.goehrs@pengutronix.de>

Thanks, applied as 2b1e5d67ce68b78d6a71fe919a8567a02096be09.

Michael

[sent from post-receive hook]

On Mon, 22 Sep 2025 13:04:19 +0200, Leonard Göhrs <l.goehrs@pengutronix.de> wrote:
> The TPM2 Feature API (FAPI) provides a more abstract view of the TPM,
> with more high level functions. To provide these it needs a bit of
> configuration and a place to store data.
> Install the default config provided by the upstream project.
> 
> Signed-off-by: Leonard Göhrs <l.goehrs@pengutronix.de>
> Message-Id: <20250917110808.167491-2-l.goehrs@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/tpm2-tss.make b/rules/tpm2-tss.make
> index 6ca5724c9c32..45fc51f1c70f 100644
> --- a/rules/tpm2-tss.make
> +++ b/rules/tpm2-tss.make
> @@ -98,6 +98,8 @@ $(STATEDIR)/tpm2-tss.targetinstall:
>  
>  	@$(call install_alternative, tpm2-tss, 0, 0, 0644, \
>  		/usr/lib/udev/rules.d/70-tpm-udev.rules)
> +	@$(call install_alternative, tpm2-tss, 0, 0, 0644, \
> +		/etc/tpm2-tss/fapi-config.json)
>  
>  	@$(call install_finish, tpm2-tss)
>  



  reply	other threads:[~2025-09-22 11:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17 11:07 [ptxdist] [PATCH 1/2] tpm2-tss: install libtss2-policy and -tcti-spi-helper Leonard Göhrs
2025-09-17 11:07 ` [ptxdist] [PATCH 2/2] tpm2-tss: install fapi-config.json Leonard Göhrs
2025-09-22 11:04   ` Michael Olbrich [this message]
2025-09-22 11:04 ` [ptxdist] [APPLIED] tpm2-tss: install libtss2-policy and -tcti-spi-helper Michael Olbrich

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=20250922110419.2076199-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=l.goehrs@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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