Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Roberto Medina <robertoxmed@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] configs/roc_pc_rk3399: Bump Linux, U-Boot, TF-A
Date: Tue, 22 Oct 2024 22:31:11 +0200	[thread overview]
Message-ID: <20241022223111.4200ccd2@windsurf> (raw)
In-Reply-To: <20241015172607.635267-1-robertoxmed@gmail.com>

Hello Roberto,

On Tue, 15 Oct 2024 18:26:07 +0100
Roberto Medina <robertoxmed@gmail.com> wrote:

> - Bump Linux to 6.6.56 (LTS).
> - Bump U-Boot to 2024.07, so it contains commit ebb0ad4eef0a ("arch: arm:
> mach-rockchip: Kconfig: Enable BOOTSTD_FULL for RK3399 and RK3588").
> - Bump TF-A to 2.11.
> 
> Signed-off-by: Roberto Medina <robertoxmed@gmail.com>
> ---
>  configs/roc_pc_rk3399_defconfig | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)

Thanks a lot for this contribution! However, we are taking advantage of
such version bumps in defconfigs to migrate them to have
BR2_DOWNLOAD_FORCE_CHECK_HASHES=y in those defconfigs. Could you try to
enable this?

./utils/add-custom-hashes will help you generate the necessary hash files.

Thanks a lot!

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

      reply	other threads:[~2024-10-22 20:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 17:26 [Buildroot] [PATCH 1/1] configs/roc_pc_rk3399: Bump Linux, U-Boot, TF-A Roberto Medina
2024-10-22 20:31 ` Thomas Petazzoni 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=20241022223111.4200ccd2@windsurf \
    --to=buildroot@buildroot.org \
    --cc=robertoxmed@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox