All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Kory Maincent via buildroot <buildroot@buildroot.org>
Cc: Kory Maincent <kory.maincent@bootlin.com>,
	Etienne Carriere <etienne.carriere@foss.st.com>
Subject: Re: [Buildroot] [PATCH 1/3] package/optee-client: Add support for custom tarball
Date: Fri, 2 Aug 2024 22:06:57 +0200	[thread overview]
Message-ID: <20240802220657.6ae4a337@windsurf> (raw)
In-Reply-To: <20240620143853.1259543-2-kory.maincent@bootlin.com>

On Thu, 20 Jun 2024 16:38:51 +0200
Kory Maincent via buildroot <buildroot@buildroot.org> wrote:

> OP-TEE OS supports custom tarballs. If the OP-TEE OS custom tarball version
> does not match the latest optee-client version supported by Buildroot,
> optee-client might not build or run properly. This patch adds support for
> an optee-client custom tarball URL to address this potential issue.
> 
> Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> ---
>  package/optee-client/Config.in       | 38 ++++++++++++++++++++++++++++
>  package/optee-client/optee-client.mk | 24 ++++++++++++++++--
>  2 files changed, 60 insertions(+), 2 deletions(-)

Thanks, series applied!

I just dropped the:

ifeq ($(BR2_PACKAGE_OPTEE_CLIENT_LATEST),y)

around the LICENSE_FILES. Indeed, we can now override the hash files in
a per-configuration basis, so this should no longer be needed.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-08-02 20:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 14:38 [Buildroot] [PATCH 0/3] Support custom tarball for OP-TEE related projects Kory Maincent via buildroot
2024-06-20 14:38 ` [Buildroot] [PATCH 1/3] package/optee-client: Add support for custom tarball Kory Maincent via buildroot
2024-07-04 14:50   ` Etienne CARRIERE - foss
2024-08-02 20:06   ` Thomas Petazzoni via buildroot [this message]
2024-06-20 14:38 ` [Buildroot] [PATCH 2/3] package/optee-test: " Kory Maincent via buildroot
2024-07-04 14:50   ` Etienne CARRIERE - foss
2024-06-20 14:38 ` [Buildroot] [PATCH 3/3] package/optee-examples: " Kory Maincent via buildroot
2024-07-04 14:50   ` Etienne CARRIERE - foss
2024-06-24  7:00 ` [Buildroot] [PATCH 0/3] Support custom tarball for OP-TEE related projects Etienne CARRIERE - foss
2024-06-28 13:55   ` Kory Maincent 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=20240802220657.6ae4a337@windsurf \
    --to=buildroot@buildroot.org \
    --cc=etienne.carriere@foss.st.com \
    --cc=kory.maincent@bootlin.com \
    --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.