All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Clément Léger" <clement.leger@bootlin.com>
Cc: Etienne Carriere <etienne.carriere@linaro.org>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3 3/7] boot/optee-os: bump to version 3.16.0
Date: Fri, 11 Mar 2022 21:47:38 +0100	[thread overview]
Message-ID: <20220311214738.5b2142e3@windsurf> (raw)
In-Reply-To: <20220311123636.13415-4-clement.leger@bootlin.com>

Hello Clément,

On Fri, 11 Mar 2022 13:36:32 +0100
Clément Léger <clement.leger@bootlin.com> wrote:

> Bump OP-TEE OS package version to OP-TEE release 3.16.0 and set
> BR2_TARGET_OPTEE_OS_NEEDS_PYTHON_CRYPTOGRAPHY default to 'y' since
> python-cryptography is now needed to build optee-os.
> 
> Acked-by: Etienne Carriere <etienne.carriere@linaro.org>
> Signed-off-by: Clément Léger <clement.leger@bootlin.com>
> ---
>  boot/optee-os/Config.in     | 5 +++--
>  boot/optee-os/optee-os.hash | 4 ++--
>  2 files changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/boot/optee-os/Config.in b/boot/optee-os/Config.in
> index f8426f9ab2..6fe2ae95ac 100644
> --- a/boot/optee-os/Config.in
> +++ b/boot/optee-os/Config.in
> @@ -18,7 +18,7 @@ choice
>  	  Select the version of OP-TEE OS you want to use
>  
>  config BR2_TARGET_OPTEE_OS_LATEST
> -	bool "3.15.0"
> +	bool "3.16.0"
>  	help
>  	  Use the latest release tag from the OP-TEE OS official Git
>  	  repository.
> @@ -50,6 +50,7 @@ endif
>  
>  config BR2_TARGET_OPTEE_OS_NEEDS_PYTHON_CRYPTOGRAPHY
>  	bool "optee-os needs host-python-cryptography to build"
> +	default y

Rather than a "default y", I would instead make
BR2_TARGET_OPTEE_OS_LATEST select
BR2_TARGET_OPTEE_OS_NEEDS_PYTHON_CRYPTOGRAPHY, so that if the latest
version of OP-TEE is used,
BR2_TARGET_OPTEE_OS_NEEDS_PYTHON_CRYPTOGRAPHY is forcefully selected.

However, you will have to propagate the
BR2_PACKAGE_HOST_RUSTC_ARCH_SUPPORTS to the OP-TEE package.

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

  reply	other threads:[~2022-03-11 20:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11 12:36 [Buildroot] [PATCH v3 0/7] boot/optee-os: support new optee-os 3.16.0 build dependencies Clément Léger via buildroot
2022-03-11 12:36 ` [Buildroot] [PATCH v3 1/7] package/python-cryptography: enable host package Clément Léger via buildroot
2022-03-11 20:43   ` Thomas Petazzoni via buildroot
2022-03-14  8:38     ` Clément Léger via buildroot
2022-03-12 14:59   ` Thomas Petazzoni via buildroot
2022-03-14  8:47     ` Clément Léger via buildroot
2022-03-11 12:36 ` [Buildroot] [PATCH v3 2/7] boot/optee-os: add support to build with python-cryptography Clément Léger via buildroot
2022-03-11 20:46   ` Thomas Petazzoni via buildroot
2022-03-11 12:36 ` [Buildroot] [PATCH v3 3/7] boot/optee-os: bump to version 3.16.0 Clément Léger via buildroot
2022-03-11 20:47   ` Thomas Petazzoni via buildroot [this message]
2022-03-11 12:36 ` [Buildroot] [PATCH v3 4/7] package/optee-test: " Clément Léger via buildroot
2022-03-11 12:36 ` [Buildroot] [PATCH v3 5/7] package/optee-examples: " Clément Léger via buildroot
2022-03-11 12:36 ` [Buildroot] [PATCH v3 6/7] package/optee-client: " Clément Léger via buildroot
2022-03-11 12:36 ` [Buildroot] [PATCH v3 7/7] package/optee-benchmark: " Clément Léger via buildroot
2022-03-12 20:36 ` [Buildroot] [PATCH v3 0/7] boot/optee-os: support new optee-os 3.16.0 build dependencies Yann E. MORIN
2022-03-14  7:38   ` Clément Léger via buildroot

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=20220311214738.5b2142e3@windsurf \
    --to=buildroot@buildroot.org \
    --cc=clement.leger@bootlin.com \
    --cc=etienne.carriere@linaro.org \
    --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 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.