From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Erik Larsson <who+buildroot@cnackers.org>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/3] package/tpm2-tools: add option for enabling FAPI tools
Date: Sat, 23 Jul 2022 14:50:49 +0200 [thread overview]
Message-ID: <20220723145049.515d8fb8@windsurf> (raw)
In-Reply-To: <e9f22a12-b37b-0dab-9a31-3c1149162e58@mind.be>
On Tue, 4 Jan 2022 18:54:41 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:
> > +ifeq ($(BR2_PACKAGE_TPM2_TOOLS_FAPI),y)
>
> Does this optoin make a big difference in size? If not, we'd normally make it
> an automatic option, i.e.
>
> ifeq ($(BR2_PACKAGE_TPM2_TSS_FAPI),y)
Erik had replied that the difference was 100KB in size, so I thought it
was worth having the extra Config.in option, and applied what Erik
proposed, with some small changes.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-23 12:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 22:38 [Buildroot] [PATCH 1/3] package/tpm2-tss: remove unused dependency Erik Larsson
2022-01-01 22:38 ` [Buildroot] [PATCH 2/3] package/tpm2-tools: bump version to 5.2 Erik Larsson
2022-01-02 4:04 ` Baruch Siach via buildroot
2022-01-02 21:25 ` Erik Larsson
2022-01-04 17:51 ` Arnout Vandecappelle
2022-01-01 22:39 ` [Buildroot] [PATCH 3/3] package/tpm2-tools: add option for enabling FAPI tools Erik Larsson
2022-01-04 17:52 ` Arnout Vandecappelle
2022-01-05 0:12 ` Erik Larsson
2022-01-04 17:54 ` Arnout Vandecappelle
2022-07-23 12:50 ` Thomas Petazzoni via buildroot [this message]
2022-07-23 12:50 ` Thomas Petazzoni via buildroot
2022-01-04 17:51 ` [Buildroot] [PATCH 1/3] package/tpm2-tss: remove unused dependency Arnout Vandecappelle
2022-01-26 20:03 ` Peter Korsgaard
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=20220723145049.515d8fb8@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@mind.be \
--cc=thomas.petazzoni@bootlin.com \
--cc=who+buildroot@cnackers.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.