From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/tpm2-tools: propagate BR2_PACKAGE_TPM2_TSS_FAPI dependencies
Date: Sat, 08 Aug 2026 16:00:14 +0200 [thread overview]
Message-ID: <e81818bf1eb94224937af525fc4392c7@free.fr> (raw)
In-Reply-To: <20260808090642.785882-1-thomas.petazzoni@bootlin.com>
On 08/08/2026 11:06, Thomas Petazzoni via buildroot wrote:
> In commit 5394df6400912efa7da4f97c7ea68a81a9f77c1d ("package/tpm2-tss:
> add Mbed-TLS crypto backend support"), a depends on
> !BR2_PACKAGE_MBEDTLS was added to BR2_PACKAGE_TPM2_TSS_FAPI, but this
> new dependency was not properly propagated to the reverse
> dependencies, causing kconfig warnings such as:
>
> WARNING: unmet direct dependencies detected for
> BR2_PACKAGE_TPM2_TSS_FAPI
> Depends on [n]: BR2_PACKAGE_TPM2_TSS [=y] && BR2_TOOLCHAIN_HAS_SYNC_4
> [=y] && !BR2_PACKAGE_MBEDTLS [=y]
> Selected by [y]:
> - BR2_PACKAGE_TPM2_TOOLS_FAPI [=y] && BR2_PACKAGE_TPM2_TOOLS [=y] &&
> BR2_TOOLCHAIN_HAS_SYNC_4 [=y]
>
> This commit properly propagates this new dependency to
> BR2_PACKAGE_TPM2_TOOLS_FAPI, fixing the kconfig warning.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Series applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-08-08 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 9:06 [Buildroot] [PATCH 1/2] package/tpm2-tools: propagate BR2_PACKAGE_TPM2_TSS_FAPI dependencies Thomas Petazzoni via buildroot
2026-08-08 9:06 ` [Buildroot] [PATCH 2/2] package/tpm2-tss: do not show comment when dependencies are not met Thomas Petazzoni via buildroot
2026-08-08 14:00 ` Julien Olivain via buildroot [this message]
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=e81818bf1eb94224937af525fc4392c7@free.fr \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.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