All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vincent Stehlé" <vincent.stehle@arm.com>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org,
	"Étienne Carrière" <etienne.carriere@foss.st.com>
Subject: Re: [Buildroot] [PATCH] boot/optee-os: add custom version option
Date: Mon, 13 Jan 2025 18:37:14 +0100	[thread overview]
Message-ID: <Z4VPSgfJCfSCixaw@debian> (raw)
In-Reply-To: <b5403f615bdbba4f0571fdefc5d16849@free.fr>

On Wed, Jan 08, 2025 at 10:51:36PM +0100, Julien Olivain wrote:
> Hi Vincent, Étienne,
> 
> On 20/12/2024 16:15, Vincent Stehlé wrote:
> > Add custom version option, to enable easily specifying an official
> > OP-TEE
> > version to use.
> > This is similar to what is done in other packages, such as linux, uboot
> > or
> > arm-trusted-firmware.
> > 
> > Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>
> > Cc: Étienne Carrière <etienne.carriere@foss.st.com>
> 
> I applied this patch to master, thanks.

Hi Julien,

Thanks for handling this patch.

> Do you think the same logic should also be added to the optee-client,
> optee-examples and optee-test packages?
> 
> I currently believe so.

Good idea!

I think we could even have an additional option in those packages to specify
"same version as optee-os", similarly to BR2_KERNEL_HEADERS_AS_KERNEL.

Best regards,
Vincent.

> 
> Best regards,
> 
> Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2025-01-13 17:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 15:15 [Buildroot] [PATCH] boot/optee-os: add custom version option Vincent Stehlé
2025-01-08 21:51 ` Julien Olivain
2025-01-13  8:04   ` Etienne CARRIERE - foss
2025-01-13 17:37   ` Vincent Stehlé [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=Z4VPSgfJCfSCixaw@debian \
    --to=vincent.stehle@arm.com \
    --cc=buildroot@buildroot.org \
    --cc=etienne.carriere@foss.st.com \
    --cc=ju.o@free.fr \
    /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.